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 "Allow trusted Microsoft Services" in Event Hub Namespace networking restrictions #7104

Closed
sebader opened this issue May 27, 2020 · 3 comments

Comments

@sebader
Copy link
Contributor

sebader commented May 27, 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

Event Hub Namespace supports to open the firewall for trusted Microsoft Services. This should be possible to set through Terraform as well
image

New or Affected Resource(s)

  • azurerm_eventhub_namespace

Potential Terraform Configuration

resource "azurerm_eventhub_namespace" "example" {
  name                = "example-namespace"
  
  network_rulesets {
    allow_trusted_microsoft_services_bypass_firewall = true
  }
}

References

@kvendingoldo
Copy link
Contributor

I started to work on this in my MR: #9038

@favoretti
Copy link
Contributor

Thanks for opening this issue! Since this issue seems to have been addressed in the latest versions of the provider (#10169) - I'm going to close it. Please open a new updated bug report if this is still relevant. Thank you.

@github-actions
Copy link

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants