-
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
Compute 2019-07-01 version #7094
Conversation
In Testing, Please Ignore[Logs] (Generated from 4c1f44f, Iteration 34).NET: test-repo-billy/azure-sdk-for-net [Logs] [Diff]
Python: test-repo-billy/azure-sdk-for-python [Logs] [Diff]
Java: test-repo-billy/azure-sdk-for-java [Logs] [Diff]JavaScript: test-repo-billy/azure-sdk-for-js [Logs] [Diff]
Go: test-repo-billy/azure-sdk-for-go [Logs] [Diff]
Ruby: test-repo-billy/azure-sdk-for-ruby [Logs] [Diff]
|
Automation for azure-sdk-for-pythonA PR has been created for you: |
Automation for azure-sdk-for-goA PR has been created for you: |
Can one of the admins verify this patch? |
c470556
to
b697336
Compare
01c84c3
to
1307bde
Compare
@zikalino Could you check why model validation fails in this PR? Thanks |
@@ -196,6 +196,20 @@ directive: | |||
- ACS service is deprecated so a PATCH endpoint won't be implemented | |||
|
|||
``` | |||
### Tag: package-2019-07 |
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.
i think we shoudl just update existing tag instead of creating a new one, or any particular reason for new one?
The reason for failure is: publicipaddressconfiguration in CreateAScaleSetWithAnAzureLoadBalancer.json |
dff17a9
to
0d2974f
Compare
…into compute-2019-07
…-api-specs into compute-2019-07
@hyonholee so we need to disable these validation errors |
@hyonholee For errors in LintDiff, if you'd like to suppress these validation errors, you may refer to specification/compute/resource-manager/readme.md of this repo and add them to the suppress part. |
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.
All swagger API specs should have a "default" response with a response body aligned to standard error contract. Can we at least add that in new/changed APIs?
specification/compute/resource-manager/Microsoft.Compute/stable/2019-07-01/compute.json
Show resolved
Hide resolved
specification/compute/resource-manager/Microsoft.Compute/stable/2019-07-01/compute.json
Show resolved
Hide resolved
specification/compute/resource-manager/Microsoft.Compute/stable/2019-07-01/disk.json
Show resolved
Hide resolved
a6358d4
to
5e46bff
Compare
5e46bff
to
b70af91
Compare
@KrisBash I added default responses to the new APIs. |
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 thanks
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.