You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Amazon.Lambda.Annotations - Support suppressing serverless.template file creation #1983
The ability to suppress the generation of the "serverless.template" file via a configuration when using Amazon.Lambda.Annotations.
Use Case
Our team's chosen IAC of choice isn't serverless (it's terraform) so we would like the ability to suppress the generation of the "serverless.template" file.
Ideally we have a choice to chose which IAC to generate but suppressing the file will be good enough for now.
@jasonmc86 Assuming in your use case terraform template would have to be manually generated, a flag/option would need to be added in global settings (refer example here) which could suppress template generation.
Feel free to contribute PR that could be reviewed by the team.
Hi, I’d be interested in implementing this. I work with C# and infrastructure as code, and the use case makes sense to me.
I’d propose an opt-in setting to suppress serverless.template generation while preserving handler generation and the current default behavior, with tests for both modes. Is there a preferred place for this setting? If this is available for a community contribution, I’d be happy to take it on.
Activity
ashishdhingra commentedon Feb 18, 2025
The
serverless.templateis written here. Should be feasible to implement the feature request. Needs review with the team.ashishdhingra commentedon Feb 20, 2025
@jasonmc86 Assuming in your use case terraform template would have to be manually generated, a flag/option would need to be added in global settings (refer example here) which could suppress template generation.
Feel free to contribute PR that could be reviewed by the team.
Thanks,
Ashish
nischaltripathi commentedon Nov 6, 2026
Hi, I’d be interested in implementing this. I work with C# and infrastructure as code, and the use case makes sense to me.
I’d propose an opt-in setting to suppress serverless.template generation while preserving handler generation and the current default behavior, with tests for both modes. Is there a preferred place for this setting? If this is available for a community contribution, I’d be happy to take it on.