-
Notifications
You must be signed in to change notification settings - Fork 1
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
Stack-action vs. action variables (TERRAFORM_APPLY | DESTROY) #14
Comments
Keep variables Remove variables Additional considerations
|
My suggestion would be to use only |
Good find! +1 to catching the corner cases + proper error reporting. Also I think it's OK that the ENV variable overrides the setting coming from config. |
I also understand that having an ENV var counterpart to the config setting is helpful when using BitOps in CI/CD and pipeline runners. This way ENV value could be changed on fly depending on context without relying on the whole config file. |
I agree with @armab that it's nice to be able to specify env vars in the pipeline config to drive behavior |
As it is right now, you can define a stack-action and yet pass TERRAFORM_APPLY / TERRAFORM_DESTROY as an environment variable. Hence, you could create the environment and destroy it in the same run.
The idea would be to:
The text was updated successfully, but these errors were encountered: