Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding s3 bucket for storing cfn template, as it is now too large to work without one #279

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

dprof-johan
Copy link
Contributor

The Command Line command recommended at the end of publish.sh no longer works, as the CFN is too large to work without specifying an S3 bucket. Added it to the command

Screenshot 2024-10-14 at 11 20 39

@@ -137,7 +137,7 @@ aws cloudformation validate-template --template-url $template > /dev/null || exi
echo "Outputs"
echo Template URL: $template
echo CF Launch URL: https://${region}.console.aws.amazon.com/cloudformation/home?region=${region}#/stacks/create/review?templateURL=${template}\&stackName=PCA
echo CLI Deploy: aws cloudformation deploy --template-file `pwd`/build/packaged.template --capabilities CAPABILITY_NAMED_IAM CAPABILITY_AUTO_EXPAND --stack-name PCA --parameter-overrides AdminEmail=YOUR_EMAIL
echo CLI Deploy: aws cloudformation deploy --template-file `pwd`/build/packaged.template --capabilities CAPABILITY_NAMED_IAM CAPABILITY_AUTO_EXPAND --stack-name PCA --s3-bucket ${BUCKET} --parameter-overrides AdminEmail=YOUR_EMAIL
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not in love with writing the template to the root of the specified bucket as a side effect of the deployment.. That might get messy.
An alternative approach could be to change this to use aws cloudformation create-stack instead, which take a [--template-url <value>] parameter which we can point to the template path $template that we already have. What do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants