Closed sixman9 closed 1 week ago
Ok, I missed samlocal deploy --help
(as opposed to simply samlocal --help
), there is mention of the --config-file
argument, however, that's not working for me:
samlocal deploy --config-file ./samconfig.toml Usage: samlocal deploy [OPTIONS] Try 'samlocal deploy --help' for help.
Error: Missing option '--stack-name', 'sam deploy --guided' can be used to provide and save needed parameters for future deploys.
Thanks for reporting @sixman9 . Can you please share some more details about your environment, as well as a small snippet of your SAM config, to help us reproduce this issue?
Error: Missing option '--stack-name', 'sam deploy --guided' can be used to provide and save needed parameters for future deploys.
Generally speaking, the samlocal
command is only a small wrapper script and should have the exact same syntax as the sam
CLI. Did you try to get it working by specifying the --stack-name
parameter..? Thanks
Hi @sixman9, quick follow-up - have you been able to get it deployed by specifying the --stack-name
parameter? Thanks for your help.
Hi! We just wanted to follow up on our last message to see whether your issue has been resolved. Were you able to get it working with the latest version of LocalStack? We would appreciate your feedback!
Closing issue due to inactivity.
My initial
samlocal deploy
hinted that I should do a guided deployment (sosamlocal deploy --guided
), after doing that I had a complete 'samconfig.toml' file, alongside my SAM 'template.yaml' file.As I'm led to believe, all I needed to do is run the
samlocal deploy
again, but it's not picking up that there is a pre-existing 'samconfig.toml' file, I'm still seeingAny ideas?
P.S. First BTW ;-P