Azure-webjobs-sdk: Reconcile IJobActivator with DI
When we did the DI work, we didn't reconcile the existing IJobActivator interface with DI. There are patterns that can be used to bridge the gap (e.g. see https://github.com/Azure/azure-webjobs-sdk/issues/1915) however, registration of a custom IJobActivator instance shouldn't be needed. Instead our activation channel should be able to just use the IServiceProvider to dynamically get instances as needed.
mathewc
All 5 comments
Is this (first class DI for functions themselves) this expected for part of initial v2 GA release?
jnevins-gcm
on 21 Sep 2018
No unfortunately, it missed the cutoff. But we'll get it in soon.
mathewc
on 21 Sep 2018
@mathewc does the change mean having a static class to host functions is no longer the way to go?
Do we now need to pay attention to Functions object lifetime?
ggirard07
on 1 Oct 2018
This issue shows closed, but I'm not quite seeing if DI is still natively supported? Is there an example of how to do dependency injection that works? I can't seem to get it going.
bryansray
on 19 Dec 2018
Also can't get it to work. Trying the sample but the constructor for Functions is not being called (which in turn makes all services null when trying to call them from triggered method).
@mathewc - Any comments on this?
Zebusch
on 20 Jun 2019
Related issues
shibayan
路
5Comments
hajekj
路
3Comments
nibras85
路
3Comments
xt0rted
路
5Comments
sergey-netdev
路
5Comments
Most helpful comment
This issue shows closed, but I'm not quite seeing if DI is still natively supported? Is there an example of how to do dependency injection that works? I can't seem to get it going.