Repository navigation
Amazon.Lambda.Annotations: allow an alternate IServiceProvider implementation #1729
Description
Describe the feature
Provide a way of using an inversion of control container other than the default Microsoft.Extensions.DependencyInjection.
Use Case
I would like to be able to use Autofac with Amazon.Lambda.Annotations.
Proposed Solution
A formal api around a Startup class would work, but it looks like a small tweak to the generated code may be sufficient to hook in an alternate IServiceProvider.
The serviceProvider is currently stored in a field defined like this:
private readonly ServiceProvider serviceProvider;
The field is using the concrete type ServiceProvider. If the field type were changed to IServiceProvider that would allow a different IServiceProvider to be used by implementing a BuildServiceProvider extension method in the Lambda project.
public static AutofacServiceProvider BuildServiceProvider(this IServiceCollection services)
{
var builder = new ContainerBuilder();
builder.Populate(services);
return new AutofacServiceProvider(builder.Build());
}
Other Information
No response
Acknowledgements
- I may be able to implement this feature request
- This feature might incur a breaking change
AWS .NET SDK and/or Package version used
Amazon.Lambda.Annotations 1.3.0
Targeted .NET Platform
.Net 8
Operating System and version
AmazonLinux
Activity
ashishdhingra commentedon Apr 15, 2024
Appears to be a useful feature request. Needs review with the team.
normj commentedon Apr 19, 2024
This is a valid feature request. We will need more upvotes to prioritize this work. If you are interested in contributing a PR to add support I would be happy to review it.
werebear73 commentedon Apr 30, 2024
Upvote
ItsSmiffy commentedon May 9, 2024
Would also like to use it with SimpleInjector. Upvote.
chrischappell-rgare commentedon Dec 2, 2025
I reviewed the generated code using the new support for ConfigureHostBuilder, hoping that would make this issue obsolete since host builder has a ConfigureContainer method. The issue still exists in the new code.
serviceProvider is still concrete type ServiceProvider. The call to BuildServiceProvider is also redundant. hostBuilder.Build builds an IServiceProvider which is available as host.Services. So, the alternate service provider can be setup by hostBuilder but it is never used by the generated code.