-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Dependencies: upgrading Azure/azure-sdk-for-go
and hashicorp/go-azure-helpers
#4775
Conversation
Acceptance Test results for this look the same as master 👍 |
Azure/azure-sdk-for-go
and hashicorp/go-azure-helpers
Azure/azure-sdk-for-go
and hashicorp/go-azure-helpers
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
This has been released in version 1.37.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 = "~> 1.37.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 👉 hashibot-feedback@hashicorp.com. Thanks! |
This PR updates the following dependencies:
github.com/Azure/azure-sdk-for-go
tov35.0.0
github.com/Azure/go-autorest
tov0.9.2
github.com/hashicorp/go-azure-helpers
tov0.10.0
The upgrade to hashicorp/go-azure-helpers includes the fix for #2602 which introduces a custom refresh function; allowing us to shell out to the Azure CLI for a replacement refresh token.
Once this PR is merged the documentation for Azure CLI authentication also needs to be updated to clarify that running longer-running tasks should be done via a Service Principal; since the refresh token itself can have custom expiry depending on the GPO's configured on the AAD Tenant (or, for example a password expiring).
Fixes #2602