Domains do not support count, making variable interpolation impossible about terraform-provider-fastly HOT 7 CLOSED

We've solved it with a separate build step in our pipeline.

We're using gomplate and template the .tf files and put something like this in them

{{ $domains := (datasource "config").domains }}{{range $domains }}
  domain = { name = "{{.}}" }
{{- end}}

The steps would be something like

1. /gomplate -f fastly.tf.tmpl -o fastly.tf -d config=config/dev.yml
2. terraform plan ...

from terraform-provider-fastly.

this issue is a duplicate of https://github.com/terraform-providers/terraform-provider-fastly/issues/2

from terraform-provider-fastly.

The same problem (no count support) also applies to... basically all the fastly resources, AFAICT. Which is rather limiting, here are some use cases:

• We want to not configure logging (bigquerylogging/gcslogging) for our staging system, but as I understand it, count is the only way to achieve an effect like if terraform.workspace == "production" with terraform.
  (For this concrete problem I'm going to try a workaround with a condition on the logging resource that always evaluates to false in staging, but that feels rather clumsy.)
• We have three backend servers for our service, whose configuration (which is quite lengthy, with SSL certificates etc.) is exactly the same, except for the hostname. It would be nice if we didn't have to copy&paste all of it three times.

from terraform-provider-fastly.

why not just allow a csv value in for now until terraform properly supports count?

from terraform-provider-fastly.

We would really like for this to be implemented we we use a large list of domains and it is becoming very unwieldy to maintain

from terraform-provider-fastly.

Could you do something like...

  dynamic "domain" {
    for_each = var.domains
    content {
      name = "${domain.value}"
    }
  }

with

variable "domains" {
  type = list(string)
  default = [ "localhost" ]
}

?

from terraform-provider-fastly.

Yes, this shouldn't be a blocker these days. Please consider using dynamic blocks.
https://www.terraform.io/docs/language/expressions/dynamic-blocks.html

#2 (comment)

Closing this issue.

from terraform-provider-fastly.