-
Notifications
You must be signed in to change notification settings - Fork 4k
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
CLI: --exclusively
is -e
for synth and deploy, but -x
for destroy
#2367
Closed
rix0rrr opened this issue
Apr 24, 2019
· 2 comments
· Fixed by #3216 or MechanicalRock/tech-radar#14 · May be fixed by MechanicalRock/cdk-constructs#5, MechanicalRock/cdk-constructs#6 or MechanicalRock/cdk-constructs#7
Closed
CLI: --exclusively
is -e
for synth and deploy, but -x
for destroy
#2367
rix0rrr opened this issue
Apr 24, 2019
· 2 comments
· Fixed by #3216 or MechanicalRock/tech-radar#14 · May be fixed by MechanicalRock/cdk-constructs#5, MechanicalRock/cdk-constructs#6 or MechanicalRock/cdk-constructs#7
Labels
Comments
rix0rrr
added
bug
This issue is a bug.
package/tools
Related to AWS CDK Tools or CLI
labels
Apr 24, 2019
Did this not change to |
You are frigging right. yargs should have told me about that, I feel :x |
rix0rrr
changed the title
Toolkit: 'cdk destroy -e stack' wants to destroy everything
CLI: Jun 26, 2019
--exclusively
is -e
for synth and deploy, but -x
for destroy
rix0rrr
added a commit
that referenced
this issue
Jul 5, 2019
Make the short option for `--exclusively` always `-e` (used to be `-e` for `synth` and `deploy`, but `-x` for `destroy). Fixes #2367.
eladb
pushed a commit
that referenced
this issue
Jul 7, 2019
Make the short option for `--exclusively` always `-e` (used to be `-e` for `synth` and `deploy`, but `-x` for `destroy). Fixes #2367.
This was referenced Aug 22, 2019
This was referenced Dec 12, 2019
This was referenced Jan 20, 2020
This was referenced Sep 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
should EXCLUSIVELY destroy
some-stack
, but in fact it wants to destroy ALL STACKS in the application. Oops.The text was updated successfully, but these errors were encountered: