-
Notifications
You must be signed in to change notification settings - Fork 313
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
Address stacks and envs by path #62
Comments
Pro this! But not sure about the |
Instead of
As in passing in a directory would be the same as |
Yeah that would be ideal. But we need to put some sort of protection around doing actions to a whole environment. It would be too easy for a user to accidentally create or update stacks unintentionally. CloudFormation slip-ups can be costly :( |
@seanrankine what about it are you not sure about? |
its in an awkward position and the word |
oh yeah I think we'd do a |
Yup but still not a huge fan of it sitting in between the command and path. It'd be nice to just tack it on the end |
I'd rather have it in front, Also, to avoid potentially harmful/accidental actions you could add a simple verification |
I like the verification step way of doing it and the safety. Thoughts @jamesroutley? Also would we want to put .yaml at the end of a stack? I'd prefer to omit it. |
I've opened an issue about adding verification to the delete commands #61. Should we add one for other commands as well? Maybe for "dangerous" commands like I put the
|
Implementation
We currently build stacks and environments with the syntax:
This proposal would change the addressing to:
Pros
zsh
onmacOS
)Cons
The text was updated successfully, but these errors were encountered: