-
Notifications
You must be signed in to change notification settings - Fork 42
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
async version of FunctionsStartup #43
Comments
@fabiocav - Is this repo no longer maintained? |
Any update on this? |
1 similar comment
Any update on this? |
@a-vishar this is something we could consider, but don't have immediate plans to address. Can you please share more details on your use case? |
Loading configurations from the blob storage or any kind of db on startup would be a(/my) use case. @fabiocav |
Prewarming (their api is async) a COSMOS client (as per their best practice doc) so that the connection is "live" for the first customer call on a premium function. |
@fabio -- wouldn't we ultimately have to wait for .NET Core to support async configuration to make it truly async? We could expose a Example: dotnet/runtime#36395, which shows that even the KeyVault config provider calls |
Currently, there would be no real benefit without proper support to make this truly asynchronous. We'll leave this open, but as stated above, this work will not be prioritized. |
dotnet/aspnetcore#24142 has some discussion for the same concern in ASP.NET Core startup which may be relevant to FunctionsStartup. |
I have code which was written async first in my
FunctionsStartup.Configure
method. I would rather not transition from sync to async and back again if I can avoid it.Similar to the introduction of
async Main
methods, would it be possible to introduce anasync Configure
method inFunctionsStartup
?The text was updated successfully, but these errors were encountered: