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

Support for eventgrid_domain_subscription #6952

Closed
Hjortsberg opened this issue May 15, 2020 · 7 comments · Fixed by #6958
Closed

Support for eventgrid_domain_subscription #6952

Hjortsberg opened this issue May 15, 2020 · 7 comments · Fixed by #6958
Labels
Milestone

Comments

@Hjortsberg
Copy link
Contributor

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

Description

We make use of event grid domains, topics and subscriptions.
However Terraform seems to lack the ability to create eventgrid domain subscriptions.
@jrauschenbusch and @katbyte has made some really welcome contributions for the ability to create event grid domains and the related topics.
We would like to be able to have Terraform provision E.g a Function and an event grid domain subscription for that function.

We have tried to set it up with a normal azurerm_eventgrid_event_subscription but then the Terraform helper resourceid.go kicks in and considers the resource-id invalid and we get a Error: ID contained more segments than required.

New or Affected Resource(s)

  • azurerm_eventgrid_domain_subscription

Potential Terraform Configuration

Currently this is what we tried and thought would work.

locals{
  index = index(data.azurerm_resources.somename.resources.*.name, var.event_domain_name)
}

resource "azurerm_eventgrid_event_subscription" "somename" {
  name  = var.event_subscription_name
  scope = "${data.azurerm_resources.somename.resources[local.index].id}/topics/sometopic"
  webhook_endpoint {
    url = "https://${var.function_app_name}.azurewebsites.net/api/RecieveEvent${var.function_secret}"
  }
}

References

@jrauschenbusch
Copy link
Contributor

@Hjortsberg
Copy link
Contributor Author

Much appriciated! 👍

@jrauschenbusch
Copy link
Contributor

jrauschenbusch commented May 16, 2020

To be more precise here. There is no new resource needed here. Should work out of the box using the already existing azurerm_eventgrid_event_subscription as soon as the fix is merged and a release is published.

Furthermore maybe this PR is of interest for you: #6860

It contains support for the azure_function_endpoint type . So if you're using an Azure function you won't need to use the webhook endpoint type anymore.

@Hjortsberg
Copy link
Contributor Author

Oh, I missed that you had implemented function endpoints too, will have to try that out!
Good to hear that we can use the azurerm_eventgrid_event_subscription when that PR is merged.

@marcin-dudek
Copy link
Contributor

If I will go back to one of previous versions will this be resolved temporarily?

@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.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants