Bring Back action UpdateHostname and UploadCertificate

[solankisamir]

We need to support updatehostname and uploadcertificate actions for one more version, to avoid customers breaking change in powershell which is built on .NET client.

These actions will be deprecated in next apiversion

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.

[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:

💡 Please review potentially introduced Error(s)/Warning(s): Analysis Report 💡

File: specification/apimanagement/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 22
After the PR: Warning(s): 0 Error(s): 24

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[solankisamir]

@sarangan12 ping!

[sarangan12]

@solankisamir Please take a look at https://travis-ci.org/Azure/azure-rest-api-specs/jobs/287657498. Your changes have caused 2 new errors which must be fixed. Please fix them and update PR

[solankisamir]

@sarangan12 I will fix the description issue, but the other issue around certificate_password naming, we had to bring back, as we need that resource in our .NET Client, which gets integrated to powershell. To make a breaking change in powershell, we need it around for one more version.

[solankisamir]

Opened issue on self #1881

[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:

💡 Please review potentially introduced Error(s)/Warning(s): Analysis Report 💡

File: specification/apimanagement/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 22
After the PR: Warning(s): 0 Error(s): 23

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[solankisamir]

@sarangan12 ping! on this. Let me know, if I am not clear.

[AutorestCI]

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

[AutorestCI]

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

[AutorestCI]

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