azure-functions-host
azure-functions-host copied to clipboard
Execution Context is not dependency Injected
Repro steps
Currently Invocation Id is part of Execution Context which cannot be Dependency Injected in Functions V2. We want to use that to insert into our downstream blob store to track as Activity Id. Due to this limitation, we had to tweak and do many workarounds. It would be great if IExecutionContext kind of interface is Dependency Injectable by default.
Expected behavior
Dependency Inject Execution Context.
Flagging feature request.
+1 for this feature to be implemented
+1 for this feature to be implemented
Could be useful for tests when trying to access headers and such that are only accessible through execution context.
+1 for this feature to be implemented
+1 for this feature to be implemented
Yes. This is very much needed.
+1 for this feature to be implemented
yes, please, +1 more to have this implemented
Related issue for isolated functions: https://github.com/Azure/azure-functions-dotnet-worker/issues/950
+1 to have this added