Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Implement a wait backoff for Key Vault LROs
See original GitHub issueConsider implementing a backoff on the polling interval for some or all Key Vault LROs. This might be most helpful for CertificateClient.StartCreateCertificate that can take a long time - even days while waiting for human intervention.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Azure Key Vault throttling guidance
On HTTP error code 429, begin throttling your client using an exponential backoff approach: Wait 1 second, retry request; If still throttled ...
Read more >How to wait till I get the secret values from Keyvault in ...
the easiest way is to use Async Await pattern, which uses promises in the background. Trying not to change your code much:
Read more >100 Ideas for Primary Teachers: Supporting Pupils with ...
Instead, you should aim to keep your tone and language low key, ... easy to forget that you asked them to leave, but...
Read more >Kafka 3.5 Documentation
Kafka combines three key capabilities so you can implement your use cases for event streaming ... For example, producers never need to wait...
Read more >The Everyday Miracle - Sep 2006 - Page 64 - Google Books Result
To do this, he had to create a machine that allowed the asphalt to move and ... If you start sliding, back off...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Valid, yes, but whether we should do anything about it in the SDK, I still think not. I think the service team should implement Retry-After so that it works with any REST client that respects it. /cc @jackrichins
@heaths is this still valid?