async version of FunctionsStartup

[a-vishar]

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 an async Configure method in FunctionsStartup?

[a-vishar]

@fabiocav - Is this repo no longer maintained?

[a-vishar]

Any update on this?

[a-vishar]

Any update on this?

[fabiocav]

@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?

[JKamsker]

Loading configurations from the blob storage or any kind of db on startup would be a(/my) use case. @fabiocav

[a-vishar]

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.

[brettsam]

@fabio -- wouldn't we ultimately have to wait for .NET Core to support async configuration to make it truly async? We could expose a Task here -- but we'd just have to call .GetAwaiter().GetResult() on it.

Example: dotnet/runtime#36395, which shows that even the KeyVault config provider calls .GetAwaiter().GetResult();

[fabiocav]

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.

[HolisticDeveloper]

dotnet/aspnetcore#24142 has some discussion for the same concern in ASP.NET Core startup which may be relevant to FunctionsStartup.