How to define optional variables in Terraform with default values defined in Consul

Maksym Demidas picture Maksym Demidas · May 22, 2018 · Viewed 16.9k times · Source

I have a Terraform script with some variables populated from Consul. I want to use this script in two different scenarios:

  • Scenario 1. Everything goes right using default values from Consul.
  • Scenario 2. I need to override some variables.

I've checked Terraform documentation and noticed that I can't use a variable defined in Consul as a default value for some another variable. So I ended up with following workaround:

## vars.tf
## emulating undefined value using "null" string
variable "my_optional_variable" { default = "null" } 

## main.tf
my_optional_variable = "${var.my_optional_variable == "null" ? data.consul_keys.my_optional_variable : var.my_optional_variable}"

Can somebody show me a better way to do it? How to avoid a hack with a "null" string?

Thanks

Answer

KCD picture KCD · Aug 9, 2018

Another option is coalesce which works with empty strings so is slightly better than your "null" string.

Given your scenario or a similar case with two variables/data sources

variable "my_default_value" {
  default = "CentOS 7"
}
variable "my_optional_variable" {
  default = ""
}

You can take the "first non-empty value from the given arguments. At least two arguments must be provided."

data "openstack_images_image_v2" "bastion_image" {
  name = "${coalesce(var.my_optional_variable, var.my_default_value)}"
}