Add new api-version 2019-06-15 of recoveryservicebackup for go sdk

[ArcturusZhang]

Latest improvements:

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Contribution checklist:

• I have reviewed the documentation for the workflow.
• Validation tools were run on swagger spec(s) and have all been fixed in this PR.
• The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

• Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
• adding/removing APIs.
• adding/removing properties.
• adding/removing API-version.
• adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

• If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
  Please follow the link to find more details on API review process.

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[allenjzhang]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[openapi-sdkautomation]

azure-sdk-for-java - Release

️✔️ succeeded [Logs] [Expand Details]

• ️✔️ Generate from 11f0576 with merge commit e61f973. SDK Automation 13.0.17.20191226.1
• ️✔️sdk/recoveryservices.backup/mgmt-v2016_08_10 [Logs]  [Release SDK Changes]
  • pom.xml
  • azure-mgmt-recoveryservices-1.0.0-beta-javadoc.jar
  • azure-mgmt-recoveryservices-1.0.0-beta-sources.jar
  • azure-mgmt-recoveryservices-1.0.0-beta.jar

[openapi-sdkautomation]

azure-sdk-for-python - Release

⚠️ warning [Logs] [Expand Details]

• ⚠️ Generate from 11f0576 with merge commit e61f973. SDK Automation 13.0.17.20191226.1

  Failed to find any diff after autorest so no changed packages was found.

[openapi-sdkautomation]

azure-sdk-for-go - Release

️✔️ succeeded [Logs] [Expand Details]

• ️✔️ Generate from 11f0576 with merge commit e61f973. SDK Automation 13.0.17.20191226.1
• ️✔️recoveryservices/mgmt/2016-06-01 [Logs]  [Release SDK Changes]
  • recoveryservices.mgmt.2016-06-01.zip
• ️✔️recoveryservices/mgmt/2016-12-01 [Logs]  [Release SDK Changes]
  • recoveryservices.mgmt.2016-12-01.zip
• ️✔️recoveryservices/mgmt/2017-07-01 [Logs]  [Release SDK Changes]
  • recoveryservices.mgmt.2017-07-01.zip
• ️✔️recoveryservices/mgmt/2019-05-13 [Logs]  [Release SDK Changes]
  • recoveryservices.mgmt.2019-05-13.zip
• ️✔️recoveryservices/mgmt/2019-06-15 [Logs]  [Release SDK Changes]
  • recoveryservices.mgmt.2019-06-15.zip

[openapi-sdkautomation]

azure-sdk-for-net - Release

️✔️ succeeded [Logs] [Expand Details]

• ️✔️ Generate from 11f0576 with merge commit e61f973. SDK Automation 13.0.17.20191226.1

  [AutoRest] realpath(): Permission denied
  [AutoRest] realpath(): Permission denied
  [AutoRest] realpath(): Permission denied
  [AutoRest] realpath(): Permission denied
  [AutoRest] realpath(): Permission denied
  [AutoRest] realpath(): Permission denied

• ️✔️Microsoft.Azure.Management.RecoveryServices.Backup [Logs]  [Release SDK Changes]
  • Microsoft.Azure.Management.RecoveryServices.Backup.4.0.1-preview.nupkg
  • Microsoft.Azure.Management.RecoveryServices.Backup.4.0.1-preview.snupkg

[openapi-sdkautomation]

azure-sdk-for-js - Release

⚠️ warning [Logs] [Expand Details]

• ⚠️ Generate from 11f0576 with merge commit e61f973. SDK Automation 13.0.17.20191226.1

  Failed to find any diff after autorest so no changed packages was found.

[ArcturusZhang]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[allenjzhang]

@ArcturusZhang Any reason that Java version is not updated as well. Looks like Java is lagging behind for quite a few package versions.

[ArcturusZhang]

This is added on demand. This api-version is requested by an email request, when I am releasing the go SDK, I noticed that the go config file does not have this api-version, therefore i added this one in this PR.
I suppose the java SDK owner will spot the same problem and submit his own PR for java new api-version when he is releasing the java SDK for the same request

[allenjzhang]

Ok, can you send an email and notify respective SDK owners? Thanks.

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).