-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
AzureRM Provider 2.34 fails to authenticate on US Government (Regression from 2.33) #9099
Comments
I tracked this down: https://github.com/Azure/go-autorest/blob/master/autorest/azure/environments.go sets all unavailable resources to "N/A" However when Synapse tokens were added to the provider, it attempts to create a client with "N/A" as the endpoint, which the hashicorp go-helpers happily pass through to It seems like these should be defaulted to "" or a more formal "N/A" model like null or optional makes sense than just a sentinel string. Or at least lazy-provision the tokens. |
@vsabella sorry for causing this regression issue for other clouds. I have submit a quick PR to fix it. |
Just to mention this also effects Azure China (Incase you were not already aware) |
No worries, I appreciate the fast response. For now we just pinned to 2.33 no problem. |
This has been released in version 2.35.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 2.35.0"
}
# ... other configuration ... |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
In the latest azurerm provider 2.34, authenticating via Azure CLI against Azure Us Government no longer works:
This does still work in azurerm provider 2.33, it is a regression in 2.34
Terraform (and AzureRM Provider) Version
Expected Result
terraform plan authorizes.
Actual Behavior
Steps to Reproduce
Debug Output
*** Azure CLI Log ***
Important Factoids
Previously Working Example
This results in a proper plan. Can be reproduced 100% of the time.
Initializing provider plugins... - Finding hashicorp/azurerm versions matching "~> 2.33.0"... - Installing hashicorp/azurerm v2.33.0... - Installed hashicorp/azurerm v2.33.0 (signed by HashiCorp)
The text was updated successfully, but these errors were encountered: