Cosmos DB - POST operation for retrieving read only keys

[dmakwana]

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

• I have read the contribution guidelines.
• My spec meets the review criteria:
  • The spec conforms to the Swagger 2.0 specification.
  • The spec follows the guidelines described in the Swagger checklist document.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.

[AutorestCI]

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

[AutorestCI]

Automation for azure-libraries-for-java

Nothing to generate for azure-libraries-for-java

[AutorestCI]

Automation for azure-sdk-for-python

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-python#2781

[AutorestCI]

Automation for azure-sdk-for-node

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-node#2728

[AutorestCI]

Automation for azure-sdk-for-go

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-go#2071

[anuchandy]

It seems both DatabaseAccounts_GetReadOnlyKeys and DatabaseAccounts_ListReadOnlyKeys returns the same result. Are we planning to deprecate one of this eventually?

[dmakwana]

Yes the GET is to be deprecated

[anuchandy]

thank you. Is this new POST action to retrieve the keys a long running operation?

[dmakwana]

No

[anuchandy]

@dmakwana any reason why we use POST for listing keys?

Adding Gaurav - @ravbhatnagar any concern here from ARM side? the context is:

1. There is already an operation to retrieve the database keys which is based on HTTP GET
2. We are introducing a new operation for retrieving the same database keys which is based on HTTP POST (this is not a long running operation)
3. The operation based on GET will be deprecated.

[ravbhatnagar]

@anuchandy - Yes, this is the right way. secrets like keys should not be exposed via a GET. Right way is through a POST. Thanks for checking!

[anuchandy]

Thanks @ravbhatnagar.

@dmakwana merging the PR.

[AutorestCI]

Automation for azure-sdk-for-java

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-java#2104