Loading...
Loading...
### Terraform Version ```shell Terraform v1.15.0 ``` ### Terraform Configuration Files ```terraform backend "azurerm" {} ``` ### Debug Output ``` shell: /usr/bin/bash -e {0} env: TERRAFORM_CLI_PATH: /actions-runner/_work/_temp/ Error: Missing required argument on main.tf line 3, in terraform: 3: backend "azurerm" {} The argument "container_name" is required, but no definition was found. Error: Missing required argument on main.tf line 3, in terraform: 3: backend "azurerm" {} The argument "key" is required, but no definition was found. Error: Missing required argument on main.tf line 3, in terraform: 3: backend "azurerm" {} The argument "storage_account_name" is required, but no definition was found. Error: Terraform exited with code 1. Error: Process completed with exit code 1. ``` ### Expected Behavior Terraform 1.15.0 should be processing my terraform just as 1.14.0 did ### Actual Behavior Terraform is failing to validate ### Steps to Reproduce 1. terraform init -input=false -backend-config=${{ mytfbackendconfiguration }} 2. terraform validate -no-color ### Additional Context I'm running terraform in a CI system and passing all required backend variables during init. It appears as though #38021 is validating the backend without considering the parameters injected during init via the `backend-config` argument. My tfbackend files include: - resource_group_name - storage_account_name - container_name - key - use_oidc - tenant_id - client_id - subscription_id As you can see this includes the `container_name`, `key`, and `storage_account_name` noted in the error message. Downgrading to a previous version of terraform works without incident. ### References - #38021 ### 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
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.