Open ljacobsson opened 2 years ago
Thanks for the feature request! We have a roadmap here, but we also try to take in popular feature requests based on 👍🏽 from the community. We will be adding this to our intake for prioritization.
@ljacobsson I believe the main drive of us not saving it before executing deployments is that if there was a working set of config, if the applied new config set broke the deployment and override the file, the working version would be lost during development, I do feel the intention here though, so maybe not changing the default behaviour and having an additional --force-save-config sort of flag to be added would be a solution. Let me know how you feel about this approach! Again I will use my try to rationalize the request with the team to see if this additional flag makes sense. If the team agrees on having this supported, will mark this as a good first issue for developer to pick up!
Describe your idea/feature/enhancement
Currently when using
sam deploy --guided
and the final steps fail for various reasons, thesamconfig.toml
file won't get written to.This is really annoying, especially for stacks with parameters.
Here's an example of me running
sam deploy --guided
with an expired SSO token. At the end of it I had nosamconfig.toml
-file and had to restart from the beginning.Proposal
Write to the file as values are entered