-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Service Bus: moved VNet and IpFilter rules from 2018-preview to 2017 API version #4245
Conversation
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-jsThe 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: |
Can one of the admins verify this patch? |
2018-preview : ARM approved PR - #3754 |
@v-Ajnava could you take a look at the few issues the CI has on this file (even if nto introduced by this very PR)? Let me know what you think, thanks! |
@lmazuel , I looked in to it, but including the 'type' missing property in spec will generate ARM error. I have removed the 'type' from example. 'type' for the DisasterRecoveryConfig is a readonly with only one enum value as 'MetadataReplication' '(in future we will be having different replication type). we will fix the RP by changing the name of property and than introduce in swagger. |
f1a36a9
to
745c49e
Compare
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.
LGTM :)
…to 2017 API version (Azure#4245)" This reverts commit 41ebc86. # Conflicts: # specification/servicebus/resource-manager/Microsoft.ServiceBus/stable/2017-04-01/servicebus.json
* flatten resources * more flattening * further flattening * more flattening * more flattening
2018-preview : ARM approved PR - #3754
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information
api-version
in the path should match theapi-version
in the spec).Quality of Swagger