-
Notifications
You must be signed in to change notification settings - Fork 724
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Location set in bootstrap is ignored - resources still deployed in us-central1 and us-west1 #1172
Labels
bug
Something isn't working
Comments
reverify after pulling also a related fix in #1181 |
verify as well 3-networks-hub-and-spoke
|
#1181 is merged |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TL;DR
Deployed with default_region = "northamerica-northeast2" in 0-bootstrap / terraform.auto.tfvars. Despite this (too many to enumerate) resources still deployed in us-central1 and us-west1. This is caused by module defaults (set in variables.tf) not being overriden when modules invoked from above
Expected behavior
Everything should be deployed in the specified region (or regions). However in terraform.auto.tfvars in 0-bootstrap we can specify a single region - while the deployment by default we specify a single region. Should have the deployment deploy in a single region, or 2 regions based exclusively on what was specified in bootstrap
Observed behavior
Here are a few examples
Terraform Configuration
Terraform Version
[user@linuxbox ~]$ terraform version Terraform v1.6.0 on linux_amd64
Additional information
Please fix region parameterization, having resources in multiple regions will make costs explode not to mention regulatory issues with data localization
The text was updated successfully, but these errors were encountered: