Skip to content
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

Feature request. Interpolations in terraform {} configuration block. #13289

Closed
DenisBY opened this issue Apr 3, 2017 · 2 comments
Closed

Feature request. Interpolations in terraform {} configuration block. #13289

DenisBY opened this issue Apr 3, 2017 · 2 comments

Comments

@DenisBY
Copy link

DenisBY commented Apr 3, 2017

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 {backend "s3" {}}

Terraform Configuration Files

terraform {
    backend "s3" {
        bucket = "tag-terraform-states"
        key = "ecs-service/${var.env_name}/${var.engine}/${var.prio}/terraform.tfstate"
        region = "${var.region}"
    }
}

Expected Behavior

Variables are interpolated to values

Actual Behavior

terraform.backend: configuration cannot contain interpolations

Steps to Reproduce

terraform plan

@jbardin
Copy link
Member

jbardin commented Apr 3, 2017

@DenisBY

Thanks for opening the issue. We are tracking this in a duplicate here: #13022.

@jbardin jbardin closed this as completed Apr 3, 2017
@ghost
Copy link

ghost commented Apr 14, 2020

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 ghost locked and limited conversation to collaborators Apr 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants