fix(ci-lease): S3 staging bucket for CFN deploy#398
Merged
Conversation
CFN requires templates >51KB to be uploaded to S3 first. Several
scenarios (council-chatbot, simply-readable, ai-contact-centre) exceed
this. Council-chatbot dispatch just hit:
Templates with a size greater than 51,200 bytes must be deployed
via an S3 Bucket. Please add the --s3-bucket parameter
Create a per-account staging bucket on demand (ndx-try-ci-cfn-stage-{acct})
because the leased pool account is wiped between leases. mb is idempotent
on existing buckets; SSE-AES256 added because S3 default since 2023.
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.
Templates >51KB need S3 staging.