Marketing Analytics Jumpstart consists of an easy, extensible and automated implementation of an end-to-end solution that enables Marketing Technology teams to store, transform, enrich with 1PD and analyze marketing data, and programmatically send predictive events to Google Analytics 4 to support conversion optimization and remarketing campaigns.
Apache License 2.0
119
stars
41
forks
source link
Fresh Installation Fails due to external data dependency only attributed at apply not at plan time #152
│ Error: Invalid for_each argument
│
│ on .terraform/modules/activation.secret_manager/main.tf line 94, in resource "google_secret_manager_secret_version" "secret-version":
│ 94: for_each = { for secret in var.secrets : secret.name => secret if can(secret.secret_data) }
│ ├────────────────
│ │ var.secrets is list of map of string with 2 elements
│
│ The "for_each" map includes keys derived from resource attributes that cannot be determined until apply, and so Terraform cannot determine the full set of keys that will
│ identify the instances of this resource.
│
│ When working with unknown values in for_each, it's better to define the map keys statically in your configuration and place apply-time results only in the map values.
│
│ Alternatively, you could use the -target planning option to first apply only the resources that the for_each value depends on, and then apply a second time to fully
│ converge.
terraform -chdir="${TERRAFORM_RUN_DIR}" apply
│ Error: Invalid for_each argument │ │ on .terraform/modules/activation.secret_manager/main.tf line 94, in resource "google_secret_manager_secret_version" "secret-version": │ 94: for_each = { for secret in var.secrets : secret.name => secret if can(secret.secret_data) } │ ├──────────────── │ │ var.secrets is list of map of string with 2 elements │ │ The "for_each" map includes keys derived from resource attributes that cannot be determined until apply, and so Terraform cannot determine the full set of keys that will │ identify the instances of this resource. │ │ When working with unknown values in for_each, it's better to define the map keys statically in your configuration and place apply-time results only in the map values. │ │ Alternatively, you could use the -target planning option to first apply only the resources that the for_each value depends on, and then apply a second time to fully │ converge.