azure-rest-api-specs icon indicating copy to clipboard operation
azure-rest-api-specs copied to clipboard

connectedvmware: fixing Swagger inconsistencies

Open tombuildsstuff opened this issue 2 years ago • 10 comments

Unblocks https://github.com/hashicorp/pandora/pull/1740

This PR fixes inconsistencies within the connectedvmware Swagger, where the URI Segments are inconsistent

tombuildsstuff avatar Oct 24 '22 13:10 tombuildsstuff

Hi, @tombuildsstuff Thanks for your PR. I am workflow bot for review process. Here are some small tips.

  • Please ensure to do self-check against checklists in first PR comment.
  • PR assignee is the person auto-assigned and responsible for your current PR reviewing and merging.
  • For specs comparison cross API versions, Use API Specs Comparison Report Generator
  • If there is CI failure(s), to fix CI error(s) is mandatory for PR merging; or you need to provide justification in PR comment for explanation. How to fix?
  • Any feedback about review process or workflow bot, pls contact swagger and tools team. [email protected]

    Swagger Validation Report

    ️❌BreakingChange: 8 Errors, 0 Warnings failed [Detail]
    compared swaggers (via Oad v0.10.1)] new version base version
    connectedvmware.json 2022-01-10-preview(bf128e1) 2022-01-10-preview(main)
    Rule Message
    1009 - RemovedRequiredParameter The required parameter 'name' was removed in the new version.
    Old: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L100:11
    1009 - RemovedRequiredParameter The required parameter 'name' was removed in the new version.
    Old: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L157:11
    1009 - RemovedRequiredParameter The required parameter 'name' was removed in the new version.
    Old: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3456:11
    1009 - RemovedRequiredParameter The required parameter 'name' was removed in the new version.
    Old: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3701:11
    1010 - AddingRequiredParameter The required parameter 'virtualMachineName' was added in the new version.
    New: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L100:11
    1010 - AddingRequiredParameter The required parameter 'virtualMachineName' was added in the new version.
    New: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L157:11
    1010 - AddingRequiredParameter The required parameter 'virtualMachineName' was added in the new version.
    New: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3456:11
    1010 - AddingRequiredParameter The required parameter 'virtualMachineName' was added in the new version.
    New: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3701:11
    ️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
    There are no breaking changes.
    ️️✔️CredScan succeeded [Detail] [Expand]
    There is no credential detected.
    ️❌LintDiff: 3 Errors, 0 Warnings failed [Detail]
    compared tags (via openapi-validator v1.13.0) new version base version
    package-2022-01-10-preview package-2022-01-10-preview(bf128e1) package-2022-01-10-preview(main)

    [must fix]The following errors/warnings are introduced by current PR:

    Rule Message Related RPC [For API reviewers]
    R4039 - ParametersOrder The parameters:resourceGroupName,name,extensionName should be kept in the same order as they present in the path.
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3510
    R4039 - ParametersOrder The parameters:resourceGroupName,name,extensionName should be kept in the same order as they present in the path.
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3577
    R4039 - ParametersOrder The parameters:resourceGroupName,name,extensionName should be kept in the same order as they present in the path.
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3632


    The following errors/warnings exist before current PR submission:

    Only 30 items are listed, please refer to log for more details.

    Rule Message
    R4041 - XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L4065
    R4041 - XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L4261
    R4041 - XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L4643
    R4041 - XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L4656
    R4041 - XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L4725
    R4041 - XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L4732
    R4041 - XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L4746
    R4041 - XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L4789
    R4041 - XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L4945
    R4041 - XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L5158
    R4041 - XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L5166
    R4041 - XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L5194
    R4041 - XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L5235
    R4041 - XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L5375
    R4041 - XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L5499
    R4041 - XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L5724
    R4041 - XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L6050
    R4041 - XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L6076
    R4041 - XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L6133
    R4041 - XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L6170
    R4041 - XmsIdentifierValidation Missing identifier id in array item property
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L6922
    :warning: R2063 - OperationIdNounConflictingModelNames OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'HybridIdentityMetadataModel'. Consider using the plural form of 'HybridIdentityMetadata' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3213
    :warning: R2063 - OperationIdNounConflictingModelNames OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'HybridIdentityMetadataModel'. Consider using the plural form of 'HybridIdentityMetadata' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3279
    :warning: R2063 - OperationIdNounConflictingModelNames OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'HybridIdentityMetadataModel'. Consider using the plural form of 'HybridIdentityMetadata' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3334
    :warning: R2063 - OperationIdNounConflictingModelNames OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'HybridIdentityMetadataModel'. Consider using the plural form of 'HybridIdentityMetadata' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3391
    :warning: R3010 - TrackedResourceListByImmediateParent The child tracked resource, 'hybridIdentityMetadata' with immediate parent 'VirtualMachine', must have a list by immediate parent operation.
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L6491
    :warning: R3010 - TrackedResourceListByImmediateParent The child tracked resource, 'extensions' with immediate parent 'VirtualMachine', must have a list by immediate parent operation.
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L6571
    :warning: R3010 - TrackedResourceListByImmediateParent The child tracked resource, 'guestAgents' with immediate parent 'VirtualMachine', must have a list by immediate parent operation.
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L6865
    :warning: R3018 - EnumInsteadOfBoolean Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: force
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L408
    :warning: R3018 - EnumInsteadOfBoolean Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: force
    Location: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L734
    ️️✔️Avocado succeeded [Detail] [Expand]
    Validation passes for Avocado.
    ️️✔️ApiReadinessCheck succeeded [Detail] [Expand]
    ️⚠️~[Staging] ServiceAPIReadinessTest: 0 Warnings warning [Detail]

    API Test is not triggered due to precheck failure. Check pipeline log for details.

    ️❌ModelValidation: 38 Errors, 0 Warnings failed [Detail]

    Only 30 items are listed, please refer to log for more details.

    Rule Message
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L108:22
    ExampleUrl: preview/2022-01-10-preview/examples/VirtualMachineAssessPatches.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L174:22
    ExampleUrl: preview/2022-01-10-preview/examples/VirtualMachineInstallPatches.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L414:22
    ExampleUrl: preview/2022-01-10-preview/examples/DeleteResourcePool.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L740:22
    ExampleUrl: preview/2022-01-10-preview/examples/DeleteCluster.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L1066:22
    ExampleUrl: preview/2022-01-10-preview/examples/DeleteHost.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L1392:22
    ExampleUrl: preview/2022-01-10-preview/examples/DeleteDatastore.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L1718:22
    ExampleUrl: preview/2022-01-10-preview/examples/DeleteVCenter.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L1989:22
    ExampleUrl: preview/2022-01-10-preview/examples/UpdateVirtualMachine.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L2061:22
    ExampleUrl: preview/2022-01-10-preview/examples/DeleteVirtualMachine.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L2123:22
    ExampleUrl: preview/2022-01-10-preview/examples/StopVirtualMachine.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L2171:22
    ExampleUrl: preview/2022-01-10-preview/examples/StartVirtualMachine.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L2219:22
    ExampleUrl: preview/2022-01-10-preview/examples/RestartVirtualMachine.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L2542:22
    ExampleUrl: preview/2022-01-10-preview/examples/DeleteVirtualMachineTemplate.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L2868:22
    ExampleUrl: preview/2022-01-10-preview/examples/DeleteVirtualNetwork.json
    REQUIRED_PARAMETER_EXAMPLE_NOT_FOUND In operation MachineExtensions_Update, parameter name is required in the swagger spec but is not present in the provided example parameter values.
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3510:16
    ExampleUrl: preview/2022-01-10-preview/examples/UpdateExtension.json#L3526:11
    REQUIRED_PARAMETER_EXAMPLE_NOT_FOUND In operation MachineExtensions_Delete, parameter name is required in the swagger spec but is not present in the provided example parameter values.
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3577:17
    ExampleUrl: preview/2022-01-10-preview/examples/DELETEExtension.json#L3593:11
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3608:22
    ExampleUrl: preview/2022-01-10-preview/examples/DELETEExtension.json
    REQUIRED_PARAMETER_EXAMPLE_NOT_FOUND In operation MachineExtensions_Get, parameter name is required in the swagger spec but is not present in the provided example parameter values.
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3632:14
    ExampleUrl: preview/2022-01-10-preview/examples/GETExtension.json#L3648:11
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3912:22
    ExampleUrl: preview/2022-01-10-preview/examples/DeleteGuestAgent.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L108:22
    ExampleUrl: preview/2022-01-10-preview/examples/VirtualMachineAssessPatches.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L174:22
    ExampleUrl: preview/2022-01-10-preview/examples/VirtualMachineInstallPatches.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L414:22
    ExampleUrl: preview/2022-01-10-preview/examples/DeleteResourcePool.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L740:22
    ExampleUrl: preview/2022-01-10-preview/examples/DeleteCluster.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L1066:22
    ExampleUrl: preview/2022-01-10-preview/examples/DeleteHost.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L1392:22
    ExampleUrl: preview/2022-01-10-preview/examples/DeleteDatastore.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L1718:22
    ExampleUrl: preview/2022-01-10-preview/examples/DeleteVCenter.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L1989:22
    ExampleUrl: preview/2022-01-10-preview/examples/UpdateVirtualMachine.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L2061:22
    ExampleUrl: preview/2022-01-10-preview/examples/DeleteVirtualMachine.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L2123:22
    ExampleUrl: preview/2022-01-10-preview/examples/StopVirtualMachine.json
    LRO_RESPONSE_HEADER Long running operation should return location or azure-AsyncOperation in header but not provided
    Url: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L2171:22
    ExampleUrl: preview/2022-01-10-preview/examples/StartVirtualMachine.json
    ️❌SemanticValidation: 6 Errors, 0 Warnings failed [Detail]
    Rule Message
    MISSING_PATH_PARAMETER_DECLARATION Path parameter is defined but is not declared: name
    JsonUrl: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3510:16
    MISSING_PATH_PARAMETER_DEFINITION Path parameter is declared but is not defined: virtualMachineName
    JsonUrl: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3510:16
    MISSING_PATH_PARAMETER_DECLARATION Path parameter is defined but is not declared: name
    JsonUrl: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3577:17
    MISSING_PATH_PARAMETER_DEFINITION Path parameter is declared but is not defined: virtualMachineName
    JsonUrl: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3577:17
    MISSING_PATH_PARAMETER_DECLARATION Path parameter is defined but is not declared: name
    JsonUrl: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3632:14
    MISSING_PATH_PARAMETER_DEFINITION Path parameter is declared but is not defined: virtualMachineName
    JsonUrl: Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json#L3632:14
    ️️✔️PoliCheck succeeded [Detail] [Expand]
    Validation passed for PoliCheck.
    ️️✔️PrettierCheck succeeded [Detail] [Expand]
    Validation passes for PrettierCheck.
    ️️✔️SpellCheck succeeded [Detail] [Expand]
    Validation passes for SpellCheck.
    ️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
    Validation passes for Lint(RPaaS).
    ️️✔️CadlValidation succeeded [Detail] [Expand]
    Validation passes for CadlValidation.
    ️️✔️PR Summary succeeded [Detail] [Expand]
    Validation passes for Summary.
    Posted by Swagger Pipeline | How to fix these errors?

    Swagger Generation Artifacts

    ️️✔️ApiDocPreview succeeded [Detail] [Expand]
     Please click here to preview with your @microsoft account. 
    ️️✔️SDK Breaking Change Tracking succeeded [Detail] [Expand]

    Breaking Changes Tracking

    ️❌ azure-sdk-for-python-track2 failed [Detail]
    • Failed [Logs] Generate from ed6827e9b1108a5b75762bd5dd67b3b4b3ad8c19. SDK Automation 14.0.0
      command	sh scripts/automation_init.sh ../azure-sdk-for-python_tmp/initInput.json ../azure-sdk-for-python_tmp/initOutput.json
      cmderr	[automation_init.sh] WARNING: Skipping azure-nspkg as it is not installed.
      command	sh scripts/automation_generate.sh ../azure-sdk-for-python_tmp/generateInput.json ../azure-sdk-for-python_tmp/generateOutput.json
      cmderr	[automation_generate.sh]
      cmderr	[automation_generate.sh] npm notice New minor version of npm available! 8.15.0 -> 8.19.2
      cmderr	[automation_generate.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.19.2>
      cmderr	[automation_generate.sh] npm notice Run `npm install -g [email protected]` to update!
      cmderr	[automation_generate.sh] npm notice
      cmdout	[automation_generate.sh] [Autorest]     - file:///mnt/vss/_work/1/s/azure-rest-api-specs/specification/connectedvmware/resource-manager/Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json:3439:5
      cmdout	[automation_generate.sh] [Autorest] fatal   | Process() cancelled due to failure
      cmdout	[automation_generate.sh] [Autorest] warning | IgnoredPropertyNextToRef | Semantic violation: Sibling values alongside $ref will be ignored. See https://github.com/Azure/autorest/blob/main/docs/openapi/howto/$ref-siblings.md for allowed values (components > schemas > GuestAgentProperties > properties > provisioningAction)
      cmdout	[automation_generate.sh] [Autorest]   keys: [ [32m'type'[39m ]
      cmdout	[automation_generate.sh] [Autorest]     - file:///mnt/vss/_work/1/s/azure-rest-api-specs/specification/connectedvmware/resource-manager/Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json:6907:9
      cmdout	[automation_generate.sh] [Autorest] error   |   Error: Semantic validation failed. There was some errors
      cmdout	[automation_generate.sh] [Autorest] error   | Autorest completed with an error. If you think the error message is unclear, or is a bug, please declare an issues at https://github.com/Azure/autorest/issues with the error message you are seeing.
      cmdout	[automation_generate.sh] [Autorest]     - file:///mnt/vss/_work/1/s/azure-rest-api-specs/specification/connectedvmware/resource-manager/Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json:3439:5
      cmdout	[automation_generate.sh] [Autorest] fatal   | Process() cancelled due to failure
      cmdout	[automation_generate.sh] [Autorest] warning | IgnoredPropertyNextToRef | Semantic violation: Sibling values alongside $ref will be ignored. See https://github.com/Azure/autorest/blob/main/docs/openapi/howto/$ref-siblings.md for allowed values (components > schemas > GuestAgentProperties > properties > provisioningAction)
      cmdout	[automation_generate.sh] [Autorest]   keys: [ [32m'type'[39m ]
      cmdout	[automation_generate.sh] [Autorest]     - file:///mnt/vss/_work/1/s/azure-rest-api-specs/specification/connectedvmware/resource-manager/Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json:6907:9
      cmdout	[automation_generate.sh] [Autorest] error   |   Error: Semantic validation failed. There was some errors
      cmdout	[automation_generate.sh] [Autorest] error   | Autorest completed with an error. If you think the error message is unclear, or is a bug, please declare an issues at https://github.com/Azure/autorest/issues with the error message you are seeing.
      cmdout	[automation_generate.sh] [Autorest]/mnt/vss/_work/1/s/azure-sdk-for-python_tmp/venv-sdk/auto_temp.json does not exist!!!Error happened during codegen
      error	Script return with result [failed] code [1] signal [null] cwd [azure-sdk-for-python]: sh scripts/automation_generate.sh
      warn	Skip package processing as generation is failed
    ️❌ azure-sdk-for-java failed [Detail]
    • Failed [Logs] Generate from ed6827e9b1108a5b75762bd5dd67b3b4b3ad8c19. SDK Automation 14.0.0
      command	./eng/mgmt/automation/init.sh ../azure-sdk-for-java_tmp/initInput.json ../azure-sdk-for-java_tmp/initOutput.json
      command	./eng/mgmt/automation/generate.py ../azure-sdk-for-java_tmp/generateInput.json ../azure-sdk-for-java_tmp/generateOutput.json
    • azure-resourcemanager-connectedvmware [View full logs]  [Preview SDK Changes]
    ️❌ azure-sdk-for-go failed [Detail]
    • Failed [Logs] Generate from ed6827e9b1108a5b75762bd5dd67b3b4b3ad8c19. SDK Automation 14.0.0
      command	sh ./eng/scripts/automation_init.sh ../../../../../azure-sdk-for-go_tmp/initInput.json ../../../../../azure-sdk-for-go_tmp/initOutput.json
      command	generator automation-v2 ../../../../../azure-sdk-for-go_tmp/generateInput.json ../../../../../azure-sdk-for-go_tmp/generateOutput.json
      cmderr	[generator automation-v2] [ERROR] total 1 error(s):
      cmderr	[generator automation-v2] [ERROR] failed to execute `go generate` '[33;1mWARNING: Unable to find version for /mnt/vss/_work/1/s/azure-sdk-for-go/src/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/connectedvmware/armconnectedvmware[0m
      cmderr	[generator automation-v2] [ERROR] Cannot find go module under resourcemanager/connectedvmware/armconnectedvmware, try to build in /mnt/vss/_work/1/s/azure-sdk-for-go/src/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/connectedvmware/armconnectedvmware
      cmderr	[generator automation-v2] [ERROR] ##[command]Cleaning auto-generated files in /mnt/vss/_work/1/s/azure-sdk-for-go/src/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/connectedvmware/armconnectedvmware
      cmderr	[generator automation-v2] [ERROR] ##[command]Executing autorest.go in  /mnt/vss/_work/1/s/azure-sdk-for-go/src/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/connectedvmware/armconnectedvmware
      cmderr	[generator automation-v2] [ERROR] autorest --version=3.8.2 --use=@autorest/[email protected] --go --track2 --output-folder=/mnt/vss/_work/1/s/azure-sdk-for-go/src/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/connectedvmware/armconnectedvmware --clear-output-folder=false --go.clear-output-folder=false --honor-body-placement=true --remove-unreferenced-types=false ./autorest.md
      cmderr	[generator automation-v2] [ERROR] AutoRest code generation utility [cli version: 3.6.1; node: v14.20.1]
      cmderr	[generator automation-v2] [ERROR] (C) 2018 Microsoft Corporation.
      cmderr	[generator automation-v2] [ERROR] https://aka.ms/autorest
      cmderr	[generator automation-v2] [ERROR] info    | AutoRest core version selected from configuration: 3.8.2.
      cmderr	[generator automation-v2] [ERROR] There is a new version of AutoRest available (3.6.2).
      cmderr	[generator automation-v2] [ERROR] > You can install the newer version with with npm install -g autorest@latest
      cmderr	[generator automation-v2] [ERROR] info    |    Loading AutoRest core      '/home/cloudtest/.autorest/@[email protected]/nodemodules/@autorest/core/dist' (3.8.2)
      cmderr	[generator automation-v2] [ERROR] info    |    Installing AutoRest extension '@autorest/go' (4.0.0-preview.44 -> 4.0.0-preview.44)
      cmderr	[generator automation-v2] [ERROR] info    |    Installed AutoRest extension '@autorest/go' (4.0.0-preview.44->4.0.0-preview.44)
      cmderr	[generator automation-v2] [ERROR] info    |    Installing AutoRest extension '@autorest/modelerfour' (4.23.1 -> 4.23.1)
      cmderr	[generator automation-v2] [ERROR] info    |    Installed AutoRest extension '@autorest/modelerfour' (4.23.1->4.23.1)
      cmderr	[generator automation-v2] [ERROR] error   | PathParameterMissingDefinition | Semantic violation: Path parameter 'virtualMachineName' referenced in path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ConnectedVMwarevSphere/virtualMachines/{virtualMachineName}/extensions/{extensionName}' needs to be defined in every operation at either the path or operation level. (Missing in 'patch', 'delete', 'get') (paths > /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ConnectedVMwarevSphere/virtualMachines/{virtualMachineName}/extensions/{extensionName})
      cmderr	[generator automation-v2] [ERROR] paramName: [32m'virtualMachineName'[39m
      cmderr	[generator automation-v2] [ERROR] uri: [32m'/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ConnectedVMwarevSphere/virtualMachines/{virtualMachineName}/extensions/{extensionName}'[39m
      cmderr	[generator automation-v2] [ERROR] methods: [ [32m'patch'[39m, [32m'delete'[39m, [32m'get'[39m ]
      cmderr	[generator automation-v2] [ERROR] - file:///mnt/vss/_work/1/s/azure-rest-api-specs/specification/connectedvmware/resource-manager/Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json:3439:5
      cmderr	[generator automation-v2] [ERROR] fatal   | Process() cancelled due to failure
      cmderr	[generator automation-v2] [ERROR] warning | IgnoredPropertyNextToRef | Semantic violation: Sibling values alongside $ref will be ignored. See https://github.com/Azure/autorest/blob/main/docs/openapi/howto/$ref-siblings.md for allowed values (components > schemas > GuestAgentProperties > properties > provisioningAction)
      cmderr	[generator automation-v2] [ERROR] keys: [ [32m'type'[39m ]
      cmderr	[generator automation-v2] [ERROR] - file:///mnt/vss/_work/1/s/azure-rest-api-specs/specification/connectedvmware/resource-manager/Microsoft.ConnectedVMwarevSphere/preview/2022-01-10-preview/connectedvmware.json:6907:9
      cmderr	[generator automation-v2] [ERROR] error   |   Error: Semantic validation failed. There was some errors
      cmderr	[generator automation-v2] [ERROR] error   | Autorest completed with an error. If you think the error message is unclear, or is a bug, please declare an issues at https://github.com/Azure/autorest/issues with the error message you are seeing.
      cmderr	[generator automation-v2] [ERROR] ##[error]Error running autorest.go
      cmderr	[generator automation-v2] [ERROR] build.go:5: running "pwsh": exit status 1
      cmderr	[generator automation-v2] [ERROR] ': exit status 1
      error	Script return with result [failed] code [1] signal [null] cwd [azure-sdk-for-go/src/github.com/Azure/azure-sdk-for-go]: generator automation-v2
      warn	Skip package processing as generation is failed
    ️❌ azure-sdk-for-js failed [Detail]
    • Failed [Logs] Generate from ed6827e9b1108a5b75762bd5dd67b3b4b3ad8c19. SDK Automation 14.0.0
      command	sh .scripts/automation_init.sh ../azure-sdk-for-js_tmp/initInput.json ../azure-sdk-for-js_tmp/initOutput.json
      warn	File azure-sdk-for-js_tmp/initOutput.json not found to read
      command	sh .scripts/automation_generate.sh ../azure-sdk-for-js_tmp/generateInput.json ../azure-sdk-for-js_tmp/generateOutput.json
      cmderr	[automation_generate.sh] [ERROR] An error occurred while generating codes for readme file: "specification/connectedvmware/resource-manager/readme.md":
      cmderr	[automation_generate.sh] [ERROR] Err: Error: Command failed: autorest --version=3.8.4 --typescript --modelerfour.lenient-model-deduplication --azure-arm --head-as-boolean=true --license-header=MICROSOFT_MIT_NO_VERSION --generate-test --typescript-sdks-folder=/mnt/vss/_work/1/s/azure-sdk-for-js ../azure-rest-api-specs/specification/connectedvmware/resource-manager/readme.md --use=@autorest/[email protected]
      cmderr	[automation_generate.sh] [ERROR] Stderr: "null"
      cmderr	[automation_generate.sh] [ERROR] Stdout: "null"
      cmderr	[automation_generate.sh] [ERROR] ErrorStack: "Error: Command failed: autorest --version=3.8.4 --typescript --modelerfour.lenient-model-deduplication --azure-arm --head-as-boolean=true --license-header=MICROSOFT_MIT_NO_VERSION --generate-test --typescript-sdks-folder=/mnt/vss/_work/1/s/azure-sdk-for-js ../azure-rest-api-specs/specification/connectedvmware/resource-manager/readme.md --use=@autorest/[email protected]
      cmderr	[automation_generate.sh] [ERROR]     at checkExecSyncError (child_process.js:790:11)
      cmderr	[automation_generate.sh] [ERROR]     at Object.execSync (child_process.js:863:15)
      cmderr	[automation_generate.sh] [ERROR]     at Object.<anonymous> (/opt/hostedtoolcache/node/14.20.1/x64/lib/node_modules/@azure-tools/js-sdk-release-tools/dist/hlc/generateMgmt.js:39:33)
      cmderr	[automation_generate.sh] [ERROR]     at Generator.next (<anonymous>)
      cmderr	[automation_generate.sh] [ERROR]     at /opt/hostedtoolcache/node/14.20.1/x64/lib/node_modules/@azure-tools/js-sdk-release-tools/node_modules/tslib/tslib.js:115:75
      cmderr	[automation_generate.sh] [ERROR]     at new Promise (<anonymous>)
      cmderr	[automation_generate.sh] [ERROR]     at Object.__awaiter (/opt/hostedtoolcache/node/14.20.1/x64/lib/node_modules/@azure-tools/js-sdk-release-tools/node_modules/tslib/tslib.js:111:16)
      cmderr	[automation_generate.sh] [ERROR]     at Object.generateMgmt (/opt/hostedtoolcache/node/14.20.1/x64/lib/node_modules/@azure-tools/js-sdk-release-tools/dist/hlc/generateMgmt.js:20:20)
      cmderr	[automation_generate.sh] [ERROR]     at /opt/hostedtoolcache/node/14.20.1/x64/lib/node_modules/@azure-tools/js-sdk-release-tools/dist/autoGenerateInPipeline.js:34:34
      cmderr	[automation_generate.sh] [ERROR]     at Generator.next (<anonymous>)"
      error	Script return with result [failed] code [1] signal [null] cwd [azure-sdk-for-js]: sh .scripts/automation_generate.sh
      warn	Skip package processing as generation is failed
    ️❌ azure-powershell failed [Detail]
    • Failed [Logs] Generate from ed6827e9b1108a5b75762bd5dd67b3b4b3ad8c19. SDK Automation 14.0.0
      command	sh ./tools/SwaggerCI/init.sh ../azure-powershell_tmp/initInput.json ../azure-powershell_tmp/initOutput.json
      command	pwsh ./tools/SwaggerCI/psci.ps1 ../azure-powershell_tmp/generateInput.json ../azure-powershell_tmp/generateOutput.json
    • Az.connectedvmware [View full logs]  [Preview SDK Changes]
    Posted by Swagger Pipeline | How to fix these errors?

    Swagger pipeline started successfully. If there is ApiView generated, it will be updated in this comment.

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

    ghost avatar Oct 24 '22 13:10 ghost

    Hi @tombuildsstuff, Your PR has some issues. Please fix the CI sequentially by following the order of Avocado, semantic validation, model validation, breaking change, lintDiff. If you have any questions, please post your questions in this channel https://aka.ms/swaggersupport.

    TaskHow to fixPriority
    AvocadoFix-AvocadoHigh
    Semantic validationFix-SemanticValidation-ErrorHigh
    Model validationFix-ModelValidation-ErrorHigh
    LintDiffFix-LintDiffhigh
    If you need further help, please feedback via swagger feedback.

    Hi @tombuildsstuff, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. Action: To initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki. If you want to know the production traffic statistic, please see ARM Traffic statistic. If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ms/swaggerfeedback. Note: To avoid breaking change, you can refer to Shift Left Solution for detecting breaking change in early phase at your service code repository.

    This PR is labeled with breaking change, please get it reviewed first

    zizw123 avatar Oct 24 '22 20:10 zizw123

    Please ensure to respond feedbacks from the ARM API reviewer. When you are ready to continue the ARM API review, please remove ARMChangesRequested

    @zizw123 there are no breaking changes in this PR

    tombuildsstuff avatar Oct 26 '22 15:10 tombuildsstuff

    ping @zizw123

    tombuildsstuff avatar Nov 04 '22 10:11 tombuildsstuff

    • @JeffreyRichter to review breaking change.

    lirenhe avatar Nov 07 '22 08:11 lirenhe

    Ping @lirenhe , is there any update on this PR? This is a blocking issue for us. Thanks!

    jiaweitao001 avatar Nov 22 '22 06:11 jiaweitao001

    Ping @lirenhe , is there any update on this PR? This is a blocking issue for us. Thanks!

    We need to required tool check pass before merging this PR and there are a lot of failures. Please check How to fix?

    lirenhe avatar Nov 23 '22 05:11 lirenhe

    Hi, @tombuildsstuff. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove no-recent-activity label.

    ghost avatar Dec 11 '22 16:12 ghost

    Waiting on the Service Team

    tombuildsstuff avatar Dec 12 '22 13:12 tombuildsstuff

    Ping @lirenhe , is there any update on this PR?

    tombuildsstuff avatar Mar 06 '23 15:03 tombuildsstuff

    Please fix the tool validation errors especially the schema validtion errors. Looks for the patch operation, paramter name of 'name' is not updated.

    lirenhe avatar Mar 07 '23 07:03 lirenhe

    From what I can see this has since been worked around on our side

    tombuildsstuff avatar Nov 13 '23 09:11 tombuildsstuff