Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EventGrid subscriptions throwing error in v2.10.0 #6962

Closed
markti opened this issue May 15, 2020 · 3 comments · Fixed by #6958
Closed

EventGrid subscriptions throwing error in v2.10.0 #6962

markti opened this issue May 15, 2020 · 3 comments · Fixed by #6958
Milestone

Comments

@markti
Copy link
Contributor

markti commented May 15, 2020

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 (and AzureRM Provider) Version

Affected Resource(s)

  • azurerm_eventgrid_event_subscription

Terraform Configuration Files

resource "azurerm_eventgrid_event_subscription" "foo_fizz_events" {
  name                 = "${var.context.app_name}-${var.context.env_name}-foo-fizz-events"
  scope                = "${module.svc_fizz_admin.topic_id}"

  webhook_endpoint {
    url = "https://${module.svc_foo_admin.hostname}/runtime/webhooks/EventGrid?functionName=${local.encounter_fizz_events}&code=${module.svc_foo_admin.function_eventgrid_key}"
  }
}

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

  1. terraform apply using 2.6.0
  2. 'terraform apply' using 2.10.0

Important Factoids

Azure Public Cloud

@jrauschenbusch
Copy link
Contributor

jrauschenbusch commented May 16, 2020

Same issue as this one: #6952

But this ticket title describes the core problem.

PR is already created.

@ghost
Copy link

ghost commented May 22, 2020

This has been released in version 2.11.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.11.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Jun 19, 2020

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!

@hashicorp hashicorp locked and limited conversation to collaborators Jun 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants