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
Error: ID contained more segments than required: "/subscriptions/{subscription_id}/resourceGroups/foo-dev-backend-us-east/providers/Microsoft.EventGrid/topics/foo-dev-bar-admin-us-east/providers/Microsoft.EventGrid/eventSubscriptions/foo-dev-bar-fizz-events"
Expected Behavior
I upgraded from 2.6.0 to 2.10.0 and i ran terraform plan with NO changes to my eventgrid subsciptions...and it should succeed without error...
Actual Behavior
throws an "ID contained more segments than required"...
Steps to Reproduce
terraform apply using 2.6.0
'terraform apply' using 2.10.0
Important Factoids
Azure Public Cloud
The text was updated successfully, but these errors were encountered:
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_eventgrid_event_subscription
Terraform Configuration Files
Panic Output
Error: ID contained more segments than required: "/subscriptions/{subscription_id}/resourceGroups/foo-dev-backend-us-east/providers/Microsoft.EventGrid/topics/foo-dev-bar-admin-us-east/providers/Microsoft.EventGrid/eventSubscriptions/foo-dev-bar-fizz-events"
Expected Behavior
I upgraded from 2.6.0 to 2.10.0 and i ran terraform plan with NO changes to my eventgrid subsciptions...and it should succeed without error...
Actual Behavior
throws an "ID contained more segments than required"...
Steps to Reproduce
terraform apply
using 2.6.0Important Factoids
Azure Public Cloud
The text was updated successfully, but these errors were encountered: