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

Add support for binding Azure Servicebus Namespace to a VNet #3930

Closed
osudude opened this issue Jul 25, 2019 · 5 comments · Fixed by #6379
Closed

Add support for binding Azure Servicebus Namespace to a VNet #3930

osudude opened this issue Jul 25, 2019 · 5 comments · Fixed by #6379

Comments

@osudude
Copy link

osudude commented Jul 25, 2019

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

Microsoft allows you to bind a Service Bus Namespace to a VNet so that service bus instance can not be accessed from other networks. This is accomplished via ARM template here. Would be nice to be able to bypass ARM template and do this using native terraform.

@SadokLadhari
Copy link

Any news about this ! can any one give me a status please ?

@ArcturusZhang
Copy link
Contributor

I am currently working on this by introducing a new resource azurerm_servicebus_namespace_network_rule

@andrew-kelleher
Copy link

@ArcturusZhang that's great! We have a need for this on my current project so will be good to see this implemented 👍

@katbyte katbyte added this to the v2.7.0 milestone Apr 21, 2020
katbyte pushed a commit that referenced this issue Apr 21, 2020
Introduces new resource azurerm_servicebus_namespace_network_rule_set

Fixes #3930
@ghost
Copy link

ghost commented Apr 23, 2020

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

@ghost
Copy link

ghost commented May 21, 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 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators May 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
5 participants