You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.
The error is from the backend part. The github action doesn't come with a managed identity by default, so just wondering if you have configured one for it?
Yes, I have configured managed identity. In that github action, right before the Terraform step, I have azure login step and this works perfectly fine:
After reading this comment #24172 (comment), my understanding is that the terraform provider uses wrong URL. This is exactly the same case as mine. But anyway, I will try to use OIDC instead.
OIDC wasn't straightforward as well. Documentation lacks information about required environment variable ARM_USE_OIDC: true I would never guess by myself as I followed the docs. I found solution in other issues: #27490 and #22034 (comment)
Yes, the endpoint under used by the backend is deprecated. The auth related code in the azurerm backend (i.e. at the terraform core) is quite out dated. The work to upgrade to match the provider is tracked at hashicorp/terraform#34322. There is an attempt from the team here, but is closed.
Is there an existing issue for this?
Community Note
Terraform Version
1.9.8
AzureRM Provider Version
3.114.0
Affected Resource(s)/Data Source(s)
provider "azurerm"
Terraform Configuration Files
Terraform config:
Expected Behaviour
No response
Actual Behaviour
No response
Steps to Reproduce
No response
Important Factoids
No response
References
This was supposed to be fixed in v3.84.0 according to #24172
The text was updated successfully, but these errors were encountered: