[x] Upgrade Terraspace: Are you using the latest version of Terraspace? This allows Terraspace to fix issues fast. There's an Upgrading Guide: https://terraspace.cloud/docs/misc/upgrading/
[x] Reproducibility: Are you reporting a bug others will be able to reproduce and not asking a question. If you're unsure or want to ask a question, do so on https://community.boltops.com
[x] Code sample: Have you put together a code sample to reproduce the issue and make it available? Code samples help speed up fixes dramatically. If it's an easily reproducible issue, then code samples are not needed. If you're unsure, please include a code sample.
My Environment
Software
Version
Operating System
Ubuntu 22.04
Terraform
v1.4.5
Terraspace
v2.2.6
Ruby
3.1.2p20
Expected Behaviour
Be able to use terraspace all plan -destroy to be able to pass the -destroy arg to terraform. Thi would result in a plan to destroy for all stacks.
Current Behavior
Running terraspace all plan -destroy results in terraspace seeing --destroy as a stack.
Log: ERROR: No stacks were found that match: --destroy
Running terraspace all plan demo -destroy results in terraspace not passing the -destory arg
Log: terraspace plan demo: Plan: 1 to add, 0 to change, 0 to destroy.
Step-by-step reproduction instructions
Simply run any terraspace all subcommand and try to pass terraform args with explicitly setting a target stack.
Example Command: terraspace all plan -destroy
Example Command: terraspace all plan demo -destroy
Code Sample
Any terraspace project will do.
Solution Suggestion
Maybe the argument mechanism could be changed so we have clear separation of parse through commands and it be fixed for the all subcommand?
Examples:
terraspace all plan -- -destroyterraspace all plan demo -- -destroyterraspace plan demo -- -destroyterraspace init demo -- -lock-timeout=0s
etc...
Checklist
My Environment
Expected Behaviour
Be able to use
terraspace all plan -destroy
to be able to pass the-destroy
arg to terraform. Thi would result in a plan to destroy for all stacks.Current Behavior
Running
terraspace all plan -destroy
results in terraspace seeing--destroy
as a stack.Log:
ERROR: No stacks were found that match: --destroy
Running
terraspace all plan demo -destroy
results in terraspace not passing the-destory
argLog:
terraspace plan demo: Plan: 1 to add, 0 to change, 0 to destroy.
Step-by-step reproduction instructions
Simply run any terraspace all subcommand and try to pass terraform args with explicitly setting a target stack.
Example Command:
terraspace all plan -destroy
Example Command:terraspace all plan demo -destroy
Code Sample
Any terraspace project will do.
Solution Suggestion
Maybe the argument mechanism could be changed so we have clear separation of parse through commands and it be fixed for the all subcommand?
Examples:
terraspace all plan -- -destroy
terraspace all plan demo -- -destroy
terraspace plan demo -- -destroy
terraspace init demo -- -lock-timeout=0s
etc...