Add proptags for codedeploy resources#3885
Merged
seshubaws merged 6 commits intoaws:developfrom Feb 18, 2026
Merged
Conversation
Member
|
I know we are fixing an error, still probably should mention this is a potential breaking change, as user could see their stack updated on re-deploy even without changes on their SAM template. |
Contributor
Author
That's a good point, can we just mention this in the release notes? |
Vandita2020
approved these changes
Feb 18, 2026
vicheey
approved these changes
Feb 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #, if available
Description of changes
There is currently no tag propagation on SAM generated CodeDeploy resources. This adds support for that
Description of how you validated changes
Ran transform on template with DeploymentPreference with PropagateTags on Function.
Existing input test of
tests/translator/input/function_with_events_and_propagate_tags.yamldoes not need to be modified as it already has DeploymentPreference with PropagateTags on Function. The output should now be different to add those tags to the generated CodeDeploy resources.Checklist
Examples?
Please reach out in the comments if you want to add an example. Examples will be
added to
sam initthrough aws/aws-sam-cli-app-templates.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.