[KeyVault] Updating resource-manager swagger to include missing defintions#2210
[KeyVault] Updating resource-manager swagger to include missing defintions#2210salameer merged 13 commits intoAzure:masterfrom
Conversation
| } | ||
| }, | ||
| "responses":{ | ||
| "200":{ |
There was a problem hiding this comment.
Vaults_CreateOrUpdate can return 201 too, please provide example response.
| } | ||
| }, | ||
| "responses":{ | ||
| "200":{ |
There was a problem hiding this comment.
Vaults_Update can return 201 too, please provide example response.
| "subscriptionId":"00000000-0000-0000-0000-000000000000", | ||
| "api-version":"2016-10-01", | ||
| "parameters":{ | ||
| "location": "westus", |
There was a problem hiding this comment.
Location isn't defined in VaultPatchParameters.
| "responses":{ | ||
| "200":{ | ||
| "headers":{}, | ||
| "body":{ |
There was a problem hiding this comment.
In Vaults_delete 200 doesn't return a body.
| } | ||
| }, | ||
| "responses": { | ||
| "200": { |
There was a problem hiding this comment.
Please add 201 response example too.
| } | ||
| }, | ||
| "responses": { | ||
| "200": { |
There was a problem hiding this comment.
Please add 201 response example.
There was a problem hiding this comment.
Sorry I missed here - also add 201 here. Signed off otherwise.
| "enabled": true, | ||
| "created": 1514940684, | ||
| "updated": 1514940698 | ||
| }, |
There was a problem hiding this comment.
Missing required property "value".
There was a problem hiding this comment.
value is not actually required in this model. I've update the model to reflect that.
| "enabled": true, | ||
| "created": 1514940950, | ||
| "updated": 1514940950 | ||
| }, |
There was a problem hiding this comment.
Missing required property "value".
There was a problem hiding this comment.
Same for listSecrets.json
There was a problem hiding this comment.
value is not actually required in this model. I've update the model to reflect that.
| "description": "Display name of log specification." | ||
| }, | ||
| "blobDuration": { | ||
| "type": "string", |
There was a problem hiding this comment.
Is this the standard TimeSpan? If so, please add "format": "duration".
| "message": { | ||
| "readOnly": true, | ||
| "type": "string", | ||
| "description": "Gets an error message explaining the Reason value in more detail." |
There was a problem hiding this comment.
Remove all the "Gets", "Sets", or "Gets or sets" in property descriptions.
|
Found some issues in the examples. The spec is mostly good. |
|
@jianghaolu All of your feedback should have been addressed here. Please let me know if you have any other concerns. |
|
@schaabs Thanks! This looks great other than one more comment here: https://github.com/Azure/azure-rest-api-specs/pull/2210/files/462e482ff6ad09a1826f2c0e04c5b7b0f027cba7#diff-713ba0219ac4cf6d8bcb48ffeb9c30cc |
| "type": { | ||
| "readOnly": true, | ||
| "type": "string", | ||
| "description": "The resource name of access policy." |
| "type": "string", | ||
| "description": "The resource name of access policy." | ||
| }, | ||
| "location": { |
There was a problem hiding this comment.
Why is location readOnly? Is this a tracked resource or proxy only?
There was a problem hiding this comment.
This is a proxy to access policies which are defined on a vault which is a tracked resource. The value for location is derived from the vault and not directly settable.
There was a problem hiding this comment.
lets remove the location property then.
|
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
|
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback Thanks for your co-operation. |
|
There were a few issues in these APIs that were discussed over email. We got an ACK from the Keyvault team on the issues and they are aware and fine with merging as is. Hence signing off. |
|
Merging this Gaurav and Jianghao are good here |
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-versionin the path should match theapi-versionin the spec).Quality of Swagger