aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
[AWS::Lambda::Version] - [Enhancement] - Auto publish Lambda Versions
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
AWS::Lambda::Version
### Resource name
_No response_
### Description
The Lambda Version resource does not support publishing new versions (e.g. when the lambda code changes) directly. Instead, users need to add a new Lambda Version resource with a changed name.
This means that there's no native way how a user could update Lambda Functions and publish the new version without requiring some sort of template pre-processing (e.g. appending the code-hash to the resource name of the Lambda Version) or using a CustomResource.
Enhancing the `AWS::Lambda::Version` resource with the ability to auto-publish new versions would simplify the management of Lambdas. While CloudFormation has workarounds, those do not work for CloudControl.
### Other Details
SAM added an [auto-publish alias feature](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-resource-function.html#sam-function-autopublishalias) to support updating the lambda code and publishing a new version. This functionality would be useful CloudControl/CloudFormation.
Contributor guide
Research direction
Start with the AWS::Lambda::Version resource behavior described in the issue and compare it with the linked SAM auto-publish alias feature. The work is done when Lambda code changes can publish a new version without requiring a changed resource name, and the behavior works for CloudControl as well as CloudFormation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100