Loading...
Loading...
### Terraform Version ```shell Terraform v1.16.5 on darwin_arm64 + provider registry.terraform.io/hashicorp/google v7.46.1 + provider registry.terraform.io/hashicorp/google-beta v7.46.1 ``` ### Terraform Configuration Files ```terraform terraform { backend "gcs" { bucket = "xxxx-xxxx" prefix = "tests" storage_custom_endpoint = "https://storage.s3nsapis.fr/storage/v1/b." } } ``` ### Debug Output ``` Error: Failed to get existing workspaces: querying Cloud Storage failed: Get "https://storage.s3nsapis.fr/storage/v1/b/xxx-xxx/o?alt=json&delimiter=%2F&endOffset=&includeFoldersAsPrefixes=false&includeTrailingDelimiter=false&matchGlob=&pageToken=&prefix=tests%2F&prettyPrint=false&projection=full&startOffset=&versions=false": the configured universe domain ("googleapis.com") does not match the universe domain found in the credentials ("s3nsapis.fr"). If you haven't configured the universe domain explicitly, "googleapis.com" is the default ``` ### Expected Behavior TF gets the states for the bucket and initialize/plan/apply ### Actual Behavior TF can't access the states because of a GCD universe mismatch ### Steps to Reproduce `terraform init` ### Additional Context The GCS backend configuration is working in terraform version <= 1.13.5. Versions >= 1.14 do not work anymore. If it's not possible to recover the former behavior, it would be great to be able to pass universe_domain as a parameter in gcs backend configuration the same way we can already do with provider configuration ### References _No response_ ### Generative AI / LLM assisted development? _No response_
Click on a version to see all relevant bugs
Terraform Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.