-
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
Virtual Network Service Endpoints for Azure CosmosDB #1342
Comments
Definitely would be useful! For anyone else looking for the ARM template "crutches" at the moment, ARM has this available via "isVirtualNetworkFilterEnabled": true,
"virtualNetworkRules": [
{
"id": "/subscriptions/guid/resourceGroups/name/providers/Microsoft.Network/virtualNetworks/vnetname/subnets/subnetname"
}
], |
Really looking forward to this feature. |
hey @idgazit @CryptonZylog @janlunddk Just to let you know that support for this has now landed in v1.16 of the AzureRM Provider (here's the full changelog](https://github.com/terraform-providers/terraform-provider-azurerm/blob/v1.16.0/CHANGELOG.md)). You can upgrade to to this version by specifying it in your provider block:
... and then running Thanks! |
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
Please add the ability to set Virtual Network Service Endpoints for Azure CosmosDB, in addition to the ip_range_filter
also to be able to configure it as a resource (external to the cosmos_db_account)
https://azure.microsoft.com/en-us/blog/virtual-network-service-endpoints-for-azure-cosmos-db-is-now-generally-available/
New or Affected Resource(s)
Potential Terraform Configuration
The text was updated successfully, but these errors were encountered: