Fabio Cavalcante
Fabio Cavalcante
@Francisco-Gamino would be good to again sync on this. Last time we discussed, the value of having this in place, in practice, was questionable.
Closing this issue as this is not something that will be done in 4.0. As mentioned above, this would be a breaking change and the recommendation is to move to...
@PureKrome that's correct. For isolated, the function payload (the code you deploy), runs outside of the host and DI in those SDKs is all based on standard .NET DI interfaces...
Had a chat with @kshyju and although it looks like we already provide the required data, there are enhancements that would make this simpler to consume. Deprioritizing this since it's...
@RohitRanjanMS will be validating to ensure this is easily done with OTel.
Thank you @mithunshanbhag for the super detailed issue! I've created an issue to track an improvement to ensure a warning is emitted in #9358 For your scenario, I'd also recommend...
@kashimiz this was still assigned to sprint 76. Was this addressed, or should I move it?
Work currently in progress, moving to sprint 96.
Providing an update here. Although the `DisabledAttribute` works in some contexts, there are several scenarios where the in-proc behavior leads to issues. In order for us to bring this functionality...
Currently blocked on a WebJobs update and fix for DI scoping (#[9852](https://github.com/Azure/azure-functions-host/issues/9852))