Skip to content

Add proptags for codedeploy resources#3885

Merged
seshubaws merged 6 commits intoaws:developfrom
seshubaws:fix/proptags
Feb 18, 2026
Merged

Add proptags for codedeploy resources#3885
seshubaws merged 6 commits intoaws:developfrom
seshubaws:fix/proptags

Conversation

@seshubaws
Copy link
Contributor

@seshubaws seshubaws commented Feb 17, 2026

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.yaml does 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 init through 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.

@seshubaws seshubaws requested a review from a team as a code owner February 17, 2026 22:54
@roger-zhangg
Copy link
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.

@seshubaws
Copy link
Contributor Author

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.

That's a good point, can we just mention this in the release notes?

@seshubaws seshubaws merged commit 0beb86e into aws:develop Feb 18, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

Comments