Skip to content

[KeyVault] Updating resource-manager swagger to include missing defintions#2210

Merged
salameer merged 13 commits intoAzure:masterfrom
schaabs:akv-mgmtfull
Jan 5, 2018
Merged

[KeyVault] Updating resource-manager swagger to include missing defintions#2210
salameer merged 13 commits intoAzure:masterfrom
schaabs:akv-mgmtfull

Conversation

@schaabs
Copy link
Copy Markdown

@schaabs schaabs commented Jan 3, 2018

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

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • If applicable, the PR references the bug/issue that it fixes.
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

@schaabs schaabs requested review from RandalliLama, dragav and seanbamsft and removed request for dragav January 3, 2018 17:25
}
},
"responses":{
"200":{
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Vaults_CreateOrUpdate can return 201 too, please provide example response.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added

}
},
"responses":{
"200":{
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Vaults_Update can return 201 too, please provide example response.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added

"subscriptionId":"00000000-0000-0000-0000-000000000000",
"api-version":"2016-10-01",
"parameters":{
"location": "westus",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Location isn't defined in VaultPatchParameters.

"responses":{
"200":{
"headers":{},
"body":{
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In Vaults_delete 200 doesn't return a body.

}
},
"responses": {
"200": {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add 201 response example too.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added

}
},
"responses": {
"200": {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add 201 response example.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry I missed here - also add 201 here. Signed off otherwise.

"enabled": true,
"created": 1514940684,
"updated": 1514940698
},
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing required property "value".

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

value is not actually required in this model. I've update the model to reflect that.

"enabled": true,
"created": 1514940950,
"updated": 1514940950
},
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing required property "value".

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same for listSecrets.json

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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."
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove all the "Gets", "Sets", or "Gets or sets" in property descriptions.

@jianghaolu
Copy link
Copy Markdown
Contributor

Found some issues in the examples. The spec is mostly good.

@schaabs
Copy link
Copy Markdown
Author

schaabs commented Jan 4, 2018

@jianghaolu All of your feedback should have been addressed here. Please let me know if you have any other concerns.

@jianghaolu
Copy link
Copy Markdown
Contributor

"type": {
"readOnly": true,
"type": "string",
"description": "The resource name of access policy."
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo in description

"type": "string",
"description": "The resource name of access policy."
},
"location": {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is location readOnly? Is this a tracked resource or proxy only?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lets remove the location property then.

@azuresdkciprbot
Copy link
Copy Markdown

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: specification/keyvault/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 12
After the PR: Warning(s): 0 Error(s): 0

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@azuresdkciprbot
Copy link
Copy Markdown

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: specification/keyvault/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 12
After the PR: Warning(s): 0 Error(s): 0

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@ravbhatnagar
Copy link
Copy Markdown
Contributor

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.

@ravbhatnagar ravbhatnagar added the ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review label Jan 5, 2018
@salameer
Copy link
Copy Markdown
Member

salameer commented Jan 5, 2018

Merging this Gaurav and Jianghao are good here

@AutorestCI
Copy link
Copy Markdown

@AutorestCI
Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants