GoogleCloudPlatform/terraform-google-secured-data-warehouse

Backward incompatible change in upstream module block deployment

LuizSDCit opened this issue · 0 comments

LuizSDCit commented

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave +1 or me too comments; they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.
  • If the issue is assigned to a user, that user is claiming responsibility for the issue.

Secured Data Warehouse Specifications

  • Version: v0.1.0
  • Platform: Linux

Terraform execution logs

Error: Invalid for_each argument

  on .terraform/modules/secured_data_warehouse.vpc_sc_bridge_confidential_data_ingestion/modules/bridge_service_perimeter/main.tf line 31, in resource "google_access_context_manager_service_perimeter_resource" "service_perimeter_resource":
  31:   for_each       = toset(formatlist("projects/%s", var.resources))

The "for_each" value depends on resource attributes that cannot be determined
until apply, so Terraform cannot predict how many instances will be created.
To work around this, use the -target argument to first apply only the
resources that the for_each depends on.


Error: Invalid for_each argument

  on .terraform/modules/secured_data_warehouse.vpc_sc_bridge_confidential_governance/modules/bridge_service_perimeter/main.tf line 31, in resource "google_access_context_manager_service_perimeter_resource" "service_perimeter_resource":
  31:   for_each       = toset(formatlist("projects/%s", var.resources))

The "for_each" value depends on resource attributes that cannot be determined
until apply, so Terraform cannot predict how many instances will be created.
To work around this, use the -target argument to first apply only the
resources that the for_each depends on.


Error: Invalid for_each argument

  on .terraform/modules/secured_data_warehouse.vpc_sc_bridge_data_ingestion_governance/modules/bridge_service_perimeter/main.tf line 31, in resource "google_access_context_manager_service_perimeter_resource" "service_perimeter_resource":
  31:   for_each       = toset(formatlist("projects/%s", var.resources))

The "for_each" value depends on resource attributes that cannot be determined
until apply, so Terraform cannot predict how many instances will be created.
To work around this, use the -target argument to first apply only the
resources that the for_each depends on.

Expected Behavior

Create the bridge with the given resources.

Actual Behavior

Receive an error related to the for_each

Steps to Reproduce.

  1. run a terraform apply on the main module

Important Factoids

It was cause by PR Ignore Changes on Resources in the terraform-google-vpc-service-controls.

References