Updating Operations API to support Python's AutoRest

[sonathan]

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.

[msftclas]

@sonathan,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

[azuresdkciprbot]

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/recoveryservices/resource-manager/readme.md
Before the PR: Warning(s): 28 Error(s): 40
After the PR: Warning(s): 28 Error(s): 40

AutoRest Linter Guidelines | AutoRest Linter Issues

Send feedback and make AutoRest Linter Azure Bot smarter day by day!

Thanks for your co-operation.

[sonathan]

@veronicagg Here is the updated PR for following: #1453

[veronicagg]

Thanks @sonathan for re-sending this PR.
We had already reviewed all content, so looks good.
Just one left over question from the other PR, which I added inline.
After confirmation on that, it can be approved and merged.
Thanks!

[veronicagg]

@sonathan per our conversation regarding this property, should thedescription be updated to include more info on what the field is expected to look? Per your comment in the referred, closed PR:
"As this field is in Response and Shoebox creates blobs in customer storage account every hour. The value PT1H indicates blobs per hour. "

[sonathan]

Thanks for pointing this out. Updated now.

[veronicagg]

Updating assignment, since I already reviewed this PR, this was just reopening it.

[azuresdkciprbot]

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/recoveryservices/resource-manager/readme.md
Before the PR: Warning(s): 28 Error(s): 40
After the PR: Warning(s): 28 Error(s): 40

AutoRest Linter Guidelines | AutoRest Linter Issues

Send feedback and make AutoRest Linter Azure Bot smarter day by day!

Thanks for your co-operation.

[sonathan]

@veronicagg Please let me know if there are still any pending changes that needs to be done before merging. Thanks a lot.

[AutorestCI]

No modification for AutorestCI/azure-sdk-for-node

[AutorestCI]

No modification for AutorestCI/azure-sdk-for-node

[AutorestCI]

Azure/azure-sdk-for-python#1411

[AutorestCI]

Azure/azure-sdk-for-ruby#945