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 dedicated eventhub clusters #6808

Closed
favoretti opened this issue May 7, 2020 · 6 comments · Fixed by #7306
Closed

Support for dedicated eventhub clusters #6808

favoretti opened this issue May 7, 2020 · 6 comments · Fixed by #7306

Comments

@favoretti
Copy link
Collaborator

favoretti commented May 7, 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

Description

I've noticed that azure-go-sdk got preview support for dedicated eventhub clusters - would it be possible to implement that resource? We're using those extensively and currently are forced to create them by hand. Moreover eventhub_namespace support max 32 partitions in hosted and unlimited in dedicated, but the resource in provider caps the partition count to 32.

@favoretti
Copy link
Collaborator Author

@mbfrahry It seems Azure/azure-sdk-for-go#8533 has been addressed, any chance you could try your changes again and if they work merge them? Thank you!

@favoretti
Copy link
Collaborator Author

@mbfrahry Tested your branch with 43.0.0 and EHC creation works.

@brandonh-msft
Copy link

Any idea when we can expect to see this in a release? Just had a look at the associated milestone and says due today. Is it on track?

@ghost
Copy link

ghost commented Jun 19, 2020

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

@favoretti
Copy link
Collaborator Author

@brandonh-msft it's released, but there's another thing that makes it tricky - namespace doesn't support assigning to the clusters yet :) see #7347

@ghost
Copy link

ghost commented Jul 17, 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!

@ghost ghost locked and limited conversation to collaborators Jul 17, 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.

4 participants