feat: add s3-bucket and s3-prefix inputs for large template upload#196
Merged
Conversation
…ws-actions#180) When s3-bucket is provided, the action uploads the local template file to S3 and uses TemplateURL instead of TemplateBody, avoiding the 51,200 byte inline template limit. Closes aws-actions#180
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.
Summary
Adds
s3-bucketands3-prefixinputs so that large templates exceeding the 51,200 byte inline limit can be automatically uploaded to S3 before creating the change set.When
s3-bucketis provided and the template is a local file, the action uploads it viaPutObjectand passesTemplateURLinstead ofTemplateBodyto CloudFormation.Closes #180
Changes
s3-bucketands3-prefixinputs@aws-sdk/client-s3dependencys3-bucketis providedUsage
Testing
All 209 tests pass.