Closed ashisa closed 4 years ago
This has been released in version 2.0.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.0.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!
Community Note
Terraform (and AzureRM Provider) Version
Affected Resource(s)
azurerm_role_assignment
Terraform Configuration Files
Debug Output
Error: authorization.RoleAssignmentsClient#Create: Failure responding to request: StatusCode=405 -- Original Error: autorest/azure: Service returned an error. Status=405 Code="" Message="The requested resource does not support http method 'PUT'."
Panic Output
None
Expected Behavior
Role assignment operation succeeds.
Actual Behavior
We get the following error - Error: authorization.RoleAssignmentsClient#Create: Failure responding to request: StatusCode=405 -- Original Error: autorest/azure: Service returned an error. Status=405 Code="" Message="The requested resource does not support http method 'PUT'."
Steps to Reproduce
terraform apply
Important Factoids
Trying to set up Atlas MongoDB on Azure as documented here - https://docs.atlas.mongodb.com/reference/api/vpc-create-peering-connection/
The steps documented on the link use Azure CLI, however, we are trying to Terraform to automate this part. All other steps work fine as mentioned above in our configuration. It's just the role assignment which fails with status 405.
References
https://docs.atlas.mongodb.com/reference/api/vpc-create-peering-connection/
0000