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

Task: CosmosDB: configure VNet rules #918

Closed
1 task
jpflueger opened this issue Apr 9, 2020 · 0 comments · Fixed by #963
Closed
1 task

Task: CosmosDB: configure VNet rules #918

jpflueger opened this issue Apr 9, 2020 · 0 comments · Fixed by #963
Assignees

Comments

@jpflueger
Copy link
Contributor

Allow the customer to configure multiple VNet rules.

Implementation Notes
We can create a list on the spec that allows users to configure multiple virtual network rules. The VirtualNetworkRules property on the CreateOrUpdate request allows you to enable network rules for multiple Virtual Network + Subnet combos using two properties:

  • ID: Resource ID of a subnet
/subscriptions/{subscriptionId}/resourceGroups/{groupName}/providers/Microsoft.Network/virtualNetworks/{virtualNetworkName}/subnets/{subnetName}
  • IgnoreMissingVNetServiceEndpoint: Create firewall rule before the virtual network has vnet service endpoint enabled.

Done criteria

  • The user is able to enable ACL rules from a Virtual Network and Subnet
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants