-
Notifications
You must be signed in to change notification settings - Fork 475
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for executable assemblies when using Lambda Annotations #1571
Comments
I have a PR ready to raise for this, just looking to get the tests working. |
Needs review with the team. @jeastham1993 Feel free to contribute PR. |
@ashishdhingra PR raised |
Closing the issue now that the PR has been merged and released. |
|
Describe the feature
The current implementation of Lambda Annotations relies on using the class based handler approach. Add support for executable assemblies so that runtimes that require the Lambda runtime to be manually bootstrapped can also be used. Behind the scenes, this will generate the static main method used as the entrypoint.
Use Case
As a developer, I want to use non-managed runtime versions of .NET but this requires me to understand how to bootstrap the runtime manually.
Proposed Solution
Update the existing source generator to generate a
Program.cs
file if targetting an executable assembly. If there are multiple handlers in the same Lambda function add an Environment Variable to determine which handler is used.Other Information
No response
Acknowledgements
AWS .NET SDK and/or Package version used
N/A, this is a new feature.
Targeted .NET Platform
.NET 6, .NET Standard 2.0
Operating System and version
All
The text was updated successfully, but these errors were encountered: