-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WintonExtensions and Polly retry policies #100
Comments
@TheDouye thanks for opening this. I've been a bit busy with other things recently, but I'll try and get back to you with a proper answer shortly. One thing that jumped to mind was that you can access the underlying If that doesn't work or is particularly cumbersome then please let me know. I'd be open to improving the functionality in this area. I think it would be good to make it possible to make the initial load more resilient if clients want that behaviour. I wouldn't want to add a direct dependency on anything like Polly though, so we'd need to find a way to create an interface enabled this. |
Hello |
Hi @TheDouye did fixed your problem? You can share with us :) |
Hi.
Not sure this is the right place to post so do not hesitate to tell me.
I would like to use a retry policy (for instance with Polly) whenever a request fails. But I'm not sure the current API allows me to do this. Or I don't know how to do it :).
So what is the best way to achieve this ?
I am able to do it in the
OnLoadException
callback by forcingcontext.Source.Build(configurationBuilder).Load()
and finally add it the currentIConfigurationBuilder
but for me we should be able to apply the policy directly on theLoad
method of theConsulConfigurationProvider
class, shouldn't we ?I can also create a
ConfigurationBuilder
and addConsulConfigurationSource
(s) only, call theBuild
method, retry as long as it fails, and finally add the created IConfiguration to the ConfigurationBuilder that will be used in my StartUp (bootstrap) class.Thx a lot and have a good day
The text was updated successfully, but these errors were encountered: