You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and ENV variable TERRAFORM_DESTROY=true the plugin runs plan -> apply -> destroy sequence which is undesired.
The expected behavior with TERRAFORM_DESTROY=true is that it'll take precedence over all the terraform stack-actions and just destroy should be executed.
Otherwise, it may lead to apply -> destroy resource recreation which could be not just a waste of time/resources, but harmful in production.
Even with an empty Terraform plugin config (defaults to plan), only destroy should be executed.
The text was updated successfully, but these errors were encountered:
When using BITOPS_TERRAFORM_COMMAND=destroy, there's a different behavior when apply is executed instead of destroy which is happening on BitOps core side (bug bitovi/bitops#371).
These are two different bugs (one in Terraform config, another in BitOps core), cross-linking for reference.
With the following
bitops.config.yaml
:and ENV variable
TERRAFORM_DESTROY=true
the plugin runsplan
->apply
->destroy
sequence which is undesired.The expected behavior with
TERRAFORM_DESTROY=true
is that it'll take precedence over all the terraformstack-actions
and justdestroy
should be executed.Otherwise, it may lead to
apply -> destroy
resource recreation which could be not just a waste of time/resources, but harmful in production.Even with an empty Terraform plugin config (defaults to
plan
), onlydestroy
should be executed.The text was updated successfully, but these errors were encountered: