Bootstrap command
https://github.com/awslabs/aws-sam-cli/blob/1c3753f2063e8769890d3a517a7a5bd26d3dd9aa/samcli/cli/command.py#L25
I would like to know why this command is only executed when sam deploy -g is done, for the first time, it should be part of the command collection, to activate it it must be done manually.
Could someone explain why?
@eliecer2000 can you please use the following parameters as explained here: https://github.com/aws/aws-sam-cli/pull/2102 and let us know if it unblocks you.
It was not explicitly added to the command collection as it was supposed to be an abstraction for sam deploy --guided, but it was always going to be something to be looked in the future.
@eliecer2000 can you please provide what your use case is, and what outcome you would like to see with this issue?
@eliecer2000 can you please provide what your use case is, and what outcome you would like to see with this issue?
Greetings, I explain the complete scenario, I develop applications based on the AWS serverless infrastructure, then I code all my components in a sam template, when I deliver it to the person who hires me, he must deploy it to the final client in your AWS account, then when you deliver that sam template it already contains a ready samconfig.toml file without the s3-bucket since it is typical of each deployment, sometimes there are endpoints in the api that do not have any protection because they are free, or any other type of configuration or confirmation question that sam-cli requests at the time of deployment, in a personal modification change the way the deployment bucket would be called, example bucket-deploy-sam-acount-<IDAcount> and set it in the configuration file, so this person who is in charge of deploying only gives the following commands,
sam build sam bootstrap sam deploy bucket-s3 bucket-deploy-sam-acount-<ID Acount>
with that I save the step of the questions of --guided
English excuse me but I reinforce myself with the google translator, and I know that sometimes you say things that are impossible to understand.
Thank you.
I'm looking at deploying an existing stack to multiple regions, and while a lot of sam configuration is reusable with minor tweaks, it would help to be able to deploy the bootstrap stack without having to tickle the sam command in just the right way.
CDK has a bootstrap command, which is quite handy. I hope we can get one here, too.
I have this need as well. In a highly locked-down account, there's permissions enough for a regular developer to deploy certain templates, but not the bootstrap template. So an admin has to go in to set that up, but can't do it without some other stack to deploy, which they don't have—they'll deploy some meaningless stack with sam deploy so that the bootstrap stack gets set up, and then delete the meaningless stack right after.
We have worked around this by having the S3 bucket created by someone else's terraform, with the same policies as sam would use. A more complete fix would be to extract the whole stack definition out of the python code and deploy it using whatever provisioning tool you deem appropriate.