Multiple Terraform States

[Jamie-BitFlight]

Hi,
We split out terraform into multiple states.
Can you query multiple terraform s3 states in a single yml deployfish file?

Jamie

[cmalek]

We also use many different state files. We usually have at least two that might be needed by deployfish:

• One that sets up the VPC (for shared resources)
• One that sets up any remaining resources for the application that have not been defined by the VPC template (for app specific resources)

We import the vpc template into the application template like so:

data "terraform_remote_state" "vpc" {
  backend = "s3"

  config {
    bucket = "terraform-statefiles"
    key    = "vpc-terraform-state"
    region = "us-west-2"
  }
}

Re-output any vpc state that deployfish might need from the application state like so:

output "rds-address-prod" {
  value = "${data.terraform_remote_state.vpc.rds-prod-address}"
}

output "rds-port-prod" {
  value = "${data.terraform_remote_state.vpc.rds-prod-port}"
}

output "elasticache-endpoint-prod" {
  value = "${data.terraform_remote_state.vpc.elasticache-prod-endpoint}"
}

And then have deployfish get all it needs from the application state file.

Would doing something like that solve your needs?

[Jamie-BitFlight]

Ah yes, that is the workaround I am using currently.

I would love to feature request this though, so that you can repeat the terraform block several times to pull values from multiple terraform states :)

[cmalek]

I'm not necessarily opposed to it. We would need to decide a policy on how to resolve what happens if multiple statefiles have outputs with the same name. We will think on it.