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.
│ Error: creating Web Hook (Subscription: "xxx"
│ Resource Group Name: "xxx"
│ Automation Account Name: "xxx"
│ Web Hook Name: "xxx"): unexpected status 400 (400 Bad Request) with response: {"Message":"Property 'runbook' cannot be updated."}
│
│ with azurerm_automation_webhook.main["xxx"],
│ on automation_webhooks.tf line 70, in resource "azurerm_automation_webhook""main":
│ 70: resource "azurerm_automation_webhook""main" {
Expected Behaviour
If this property cannot be updated, then I expect this resource to be rebuilt afresh to accommodate for the change in name
Actual Behaviour
Terraform plans show this will be modified, on apply ARM returns an error with a 400 status code
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Community Note
Terraform Version
1.9.5
AzureRM Provider Version
4.0.1
Affected Resource(s)/Data Source(s)
azurerm_automation_webhook
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
If this property cannot be updated, then I expect this resource to be rebuilt afresh to accommodate for the change in name
Actual Behaviour
Terraform plans show this will be modified, on apply ARM returns an error with a 400 status code
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: