-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
[ACR] Add IP rules #4895
[ACR] Add IP rules #4895
Conversation
If you're a MSFT employee, click this link |
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-rubyThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-nodeThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-javaThe initial PR has been merged into your service PR: |
Can one of the admins verify this patch? |
This is a subsequent PR of #4506 As requested by Azure Network Team, we have to support IP rules together with virtual network rules to ship this feature. @ravbhatnagar As agreed earlier with this issue #4625 Adding these properties won't be a breaking change to this api-version. We will release a new api-version (presumably |
@ravbhatnagar please sign-off |
}, | ||
"value": { | ||
"description": "Specifies the IP or IP range in CIDR format. Only IPV4 address is allowed.", | ||
"type": "string" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think it would be useful to apply following attribute
"x-ms-client-name": "IPAddressOrRange"
that way generated code is consistent with the same feature from other service? e.g. here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated
Automation for azure-sdk-for-jsThe initial PR has been merged into your service PR: |
Signing off from ARM side as we already have an issue to track the PUT behavior. |
* Add IP rules * Remove chart actions * Add x-ms-client-name
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.