-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Comments
Any news about this ! can any one give me a status please ? |
I am currently working on this by introducing a new resource |
@ArcturusZhang that's great! We have a need for this on my current project so will be good to see this implemented 👍 |
Introduces new resource azurerm_servicebus_namespace_network_rule_set Fixes #3930
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 ... |
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! |
Community Note
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.
The text was updated successfully, but these errors were encountered: