Batch link to vcenter

[nascarsayan]

---

• Add command az connectedvmware create-from-machines.
• Delete HCRP Machine resource by default during delete vm. To retain, use --retain-machine flag.
• Use GA API Version for VCENTER_KIND_GET_API_VERSION.
• Set extension to non-preview and update version to 1.0.0

Related command

az connectedvmware

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[azure-client-tools-bot-prd]

⚠️Azure CLI Extensions Breaking Change Test

⚠️connectedvmware

rule	cmd_name	rule_message	suggest_message
⚠️ 1001 - CmdAdd	connectedvmware vm create-from-machines	cmd connectedvmware vm create-from-machines added
⚠️ 1006 - ParaAdd	connectedvmware vm delete	cmd connectedvmware vm delete added parameter retain_machine

[azure-client-tools-bot-prd]

Hi @nascarsayan,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[yonzhan]

Please fix CI issues.

[nascarsayan]

Please fix CI issues.

The CI failure looks to be unrelated to the code changes. It failed because it was unable to authenticate to the nuget endpoint while downloading the CredScan tool. Link

Pipeline failures started 2 days back - I can see other PRs failing with same error.

Attempting to gather dependency information for package 'Microsoft.Security.CredScan.2.1.17' with respect to project 'D:\a\_work\_sdt', targeting 'Any,Version=v0.0'
MSBuild auto-detection: using msbuild version '16.11.2.50704' from 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\bin'.
Using credentials from config. UserName: VssSessionToken
WARNING: The plugin credential provider could not acquire credentials. Authentication may require manual action. Consider re-running the command with --interactive for `dotnet`, /p:NuGetInteractive="true" for MSBuild or removing the -NonInteractive switch for `NuGet`
Unable to load the service index for source https://pkgs.dev.azure.com/secdevtools/_packaging/SecDevTools/nuget/v3/index.json.
  Response status code does not indicate success: 401 (Unauthorized).
##[command]"NuGet.exe" install Microsoft.Security.CredScan -Source https://pkgs.dev.azure.com/secdevtools/_packaging/SecDevTools/nuget/v3/index.json -Version 2.1.17 -ConfigFile D:\a\_work\_sdt\dt.nuget.config -NonInteractive

[wangzelin007]

Please fix CI issues.

The CI failure looks to be unrelated to the code changes. It failed because it was unable to authenticate to the nuget endpoint while downloading the CredScan tool. Link

Pipeline failures started 2 days back - I can see other PRs failing with same error.

Attempting to gather dependency information for package 'Microsoft.Security.CredScan.2.1.17' with respect to project 'D:\a\_work\_sdt', targeting 'Any,Version=v0.0'
MSBuild auto-detection: using msbuild version '16.11.2.50704' from 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\bin'.
Using credentials from config. UserName: VssSessionToken
WARNING: The plugin credential provider could not acquire credentials. Authentication may require manual action. Consider re-running the command with --interactive for `dotnet`, /p:NuGetInteractive="true" for MSBuild or removing the -NonInteractive switch for `NuGet`
Unable to load the service index for source https://pkgs.dev.azure.com/secdevtools/_packaging/SecDevTools/nuget/v3/index.json.
  Response status code does not indicate success: 401 (Unauthorized).
##[command]"NuGet.exe" install Microsoft.Security.CredScan -Source https://pkgs.dev.azure.com/secdevtools/_packaging/SecDevTools/nuget/v3/index.json -Version 2.1.17 -ConfigFile D:\a\_work\_sdt\dt.nuget.config -NonInteractive

We have sent an email to Microsoft Security Code Analysis Support for help, thank you for your reminder.

[jsntcy]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[wangzelin007]

Add @yanzhudd and @ReaNAiveD to help review this PR.

[yanzhudd]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[yanzhudd]

Please fix the CI issues.

[nascarsayan]

Please fix the CI issues.

All the failures are happening due to appservice-kube extension, which were not happening before. The failures might be happening because this PR got merged without the CI build tests running?

[yanzhudd]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[yanzhudd]

The CI has passed after re-running.

[azclibot]

[Release] Update index.json for extension [ connectedvmware ] : https://dev.azure.com/azclitools/internal/_build/results?buildId=135724&view=results