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
It would be very useful to have support of variables in terraform {} configuration block.
In my case I use one state to manage many ECS Services. They are mostly the same but with few differences like name(engine), priority, etc. and of course I have these services on different environments, like DEV or PROD.
I know that I can use empty terraform { backend “s3” {} } and then use -backend-config in command line to provide values, but It would be nice to provide values for variable only once.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 14, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be very useful to have support of variables in terraform {} configuration block.
In my case I use one state to manage many ECS Services. They are mostly the same but with few differences like name(engine), priority, etc. and of course I have these services on different environments, like DEV or PROD.
I know that I can use empty
terraform { backend “s3” {} }
and then use-backend-config
in command line to provide values, but It would be nice to provide values for variable only once.Terraform Version
Terraform v0.9.2
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
Variables are interpolated to values
Actual Behavior
terraform.backend: configuration cannot contain interpolations
Steps to Reproduce
terraform plan
The text was updated successfully, but these errors were encountered: