Terraform-provider-azurerm: AzureRM provider in Azure Cloud Shell error

Created on 11 Oct 2018  ·  4Comments  ·  Source: terraform-providers/terraform-provider-azurerm

Community Note

  • 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 "+1" or "me too" comments, 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

Terraform Version

Terraform v0.11.8

  • provider.azurerm v1.13.0

Also occurs with provider.azurerm v1.16.0

Affected Resource(s)

  • provider.azurerm

Terraform Configuration Files

provider "azurerm" {

}
resource "azurerm_resource_group" "Default" {
  name     = "Testnsg"
  location = "EastUS"
}

Debug Output

https://gist.github.com/jeffwmiles/ac59597be7ac9d61184b713e2c1ad3b0

Panic Output

Expected Behavior

As per Microsoft Doc on using Terraform with Azure Cloud Shell, expecting no additional parameters needed for the AzureRm provider, and it successfully completing "terraform plan".

This appeared to be working as recent as last week, with no change in terraform files.

Actual Behavior

See debug output.

Steps to Reproduce

  1. Start Azure Cloud Shell
  2. Perform terraform init and note it succeeds
  3. Perform terraform apply

Important Factoids

This error now occurs across multiple subscriptions, with both remote and local backend.

References

  • #0000
authentication bug microsof1

All 4 comments

@jeffwmiles Thanks for reporting this issue. It's a regression for Cloud Shell, we're rolling out the hotfix. Please retry it after 24 hours.

Thanks @metacpp, after testing this evening I can confirm that Terraform within Azure Cloud Shell is functioning again as expected.

@jeffwmiles thanks for confirming that, glad to hear this is now working for you - I'm going to close this issue for the moment. Thanks!

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!

Was this page helpful?
0 / 5 - 0 ratings