Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add AppPlatform 2024-07-01-preview #29179

Conversation

smile37773
Copy link
Member

@smile37773 smile37773 commented May 21, 2024

ARM (Control Plane) API Specification Update Pull Request

Tip

Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

spec_pr_review_workflow_diagram

Purpose of this PR

What's the purpose of this PR? Check the specific option that applies. This is mandatory!

  • New resource provider.
  • New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
  • Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
  • Update existing version to fix OpenAPI spec quality issues in S360.
  • Other, please clarify:
    • edit this with your clarification

Due diligence checklist

To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

  • I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
  • I have reviewed following Resource Provider guidelines, including
    ARM resource provider contract and
    REST guidelines (estimated time: 4 hours).
    I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

  • First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
  • To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
  • For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
    and https://aka.ms/ci-fix.
  • For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
  • If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
    This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
  • If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Copy link

Hi @smile37773, this service has enabled ShiftLeft Toolset. All spec updates MUST be initiated from service ADO project repo, so that to guarantee it to be the source of truth., please review this pull request if it is intentional or reject it if it is not expected. Normally, all the specification or example changes should start with PR created in ADO.

  • You can refer to ShiftLeft Toolset Introduction for details.
  • Please contact service focal contacts or ShiftLeft Toolset Support Channel if need further help.
  • Copy link

    openapi-pipeline-app bot commented May 21, 2024

    Next Steps to Merge

    Next steps that must be taken to merge this PR:
    • ❌ This PR is in purview of the ARM review (label: ARMReview). This PR must get ARMSignedOff label from an ARM reviewer.
      This PR is awaiting ARM reviewer feedback (label: WaitForARMFeedback).
      To learn when this PR will get reviewed, see ARM review queue at aka.ms/azsdk/pr-arm-review
      For details of the ARM review, see aka.ms/azsdk/pr-arm-review
    • ❌ The required check named Automated merging requirements met has failed. This is the final check that must pass. Refer to the check in the PR's 'Checks' tab for details on how to fix it. In addition, refer to step 4 in the PR workflow diagram

    Copy link

    openapi-pipeline-app bot commented May 21, 2024

    Swagger Validation Report

    ️️✔️BreakingChange succeeded [Detail] [Expand]
    There are no breaking changes.
    ️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
    There are no breaking changes.
    Compared specs (v0.10.9) new version base version
    appplatform.json 2024-07-01-preview(bbaea0a) 2023-12-01(main)
    appplatform.json 2024-07-01-preview(bbaea0a) 2024-05-01-preview(main)
    ️️✔️CredScan succeeded [Detail] [Expand]
    There is no credential detected.
    ️⚠️LintDiff: 0 Warnings warning [Detail]
    Compared specs (v2.2.2) new version base version
    package-preview-2024-07 package-preview-2024-07(bbaea0a) default(main)

    The following errors/warnings exist before current PR submission:

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

    Rule Message
    PutResponseCodes Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L63
    LroLocationHeader A 202 response should include an Location response header.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L105
    DeleteResponseCodes Long-running delete operations must have responses with 202, 204 and default return codes. They also must have no other response codes.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L134
    LroLocationHeader A 202 response should include an Location response header.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L158
    UnSupportedPatchProperties Mark the top-level property 'location', specified in the patch operation body, as readOnly or immutable. You could also choose to remove it from the request payload of the Patch operation. This property is not patchable.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L197
    PatchBodyParametersSchema Properties of a PATCH request body must not be required, property:type.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L202
    PatchBodyParametersSchema Properties of a PATCH request body must not be required, property:frequency.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L202
    PatchBodyParametersSchema Properties of a PATCH request body must not have default value, property:name.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L202
    PatchBodyParametersSchema Properties of a PATCH request body must not have default value, property:tier.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L202
    LroLocationHeader A 202 response should include an Location response header.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L214
    PostResponseCodes Long-running POST operations must have responses with 202 and default return codes. They must also have a 200 return code if only if the final response is intended to have a schema, if not the 200 return code must not be specified. They also must not have other response codes.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L410
    LroLocationHeader A 202 response should include an Location response header.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L431
    NoErrorCodeResponses Invalid status code specified. Please refer to the documentation for the allowed set.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L434
    NoErrorCodeResponses Invalid status code specified. Please refer to the documentation for the allowed set.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L438
    PostResponseCodes Long-running POST operations must have responses with 202 and default return codes. They must also have a 200 return code if only if the final response is intended to have a schema, if not the 200 return code must not be specified. They also must not have other response codes.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L458
    LroLocationHeader A 202 response should include an Location response header.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L479
    NoErrorCodeResponses Invalid status code specified. Please refer to the documentation for the allowed set.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L482
    NoErrorCodeResponses Invalid status code specified. Please refer to the documentation for the allowed set.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L486
    PostResponseCodes 200 return code does not have a schema specified. LRO POST must have a 200 return code if only if the final response is intended to have a schema, if not the 200 return code must not be specified.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L641
    PostResponseCodes 200 return code does not have a schema specified. LRO POST must have a 200 return code if only if the final response is intended to have a schema, if not the 200 return code must not be specified.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L701
    XmsPageableForListCalls x-ms-pageable extension must be specified for LIST APIs.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L1007
    EvenSegmentedPathForPutOperation API path with PUT operation defined MUST have even number of segments (i.e. end in {resourceType}/{resourceName} segments).
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L1048
    XmsPageableForListCalls x-ms-pageable extension must be specified for LIST APIs.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L1049
    EvenSegmentedPathForPutOperation API path with PUT operation defined MUST have even number of segments (i.e. end in {resourceType}/{resourceName} segments).
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L1218
    XmsPageableForListCalls x-ms-pageable extension must be specified for LIST APIs.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L1219
    ProvisioningStateSpecifiedForLROPut 201 response schema in long running PUT operation is missing ProvisioningState property. A LRO PUT operations response schema must have ProvisioningState specified for the 200 and 201 status codes.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L1262
    PutResponseCodes Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L1262
    LroLocationHeader A 202 response should include an Location response header.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L1298
    PatchBodyParametersSchema Properties of a PATCH request body must not be required, property:uri.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L1345
    LroLocationHeader A 202 response should include an Location response header.
    Location: Microsoft.AppPlatform/preview/2024-07-01-preview/appplatform.json#L1357
    ️️✔️Avocado succeeded [Detail] [Expand]
    Validation passes for Avocado.
    ️️✔️SwaggerAPIView succeeded [Detail] [Expand]
    ️️✔️TypeSpecAPIView succeeded [Detail] [Expand]
    ️️✔️ModelValidation succeeded [Detail] [Expand]
    Validation passes for ModelValidation.
    ️️✔️SemanticValidation succeeded [Detail] [Expand]
    Validation passes for SemanticValidation.
    ️️✔️PoliCheck succeeded [Detail] [Expand]
    Validation passed for PoliCheck.
    ️️✔️SpellCheck succeeded [Detail] [Expand]
    Validation passes for SpellCheck.
    ️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
    Validation passes for Lint(RPaaS).
    ️️✔️PR Summary succeeded [Detail] [Expand]
    Validation passes for Summary.
    ️️✔️Automated merging requirements met succeeded [Detail] [Expand]
    Posted by Swagger Pipeline | How to fix these errors?

    Copy link

    openapi-pipeline-app bot commented May 21, 2024

    Swagger Generation Artifacts

    ️️✔️ApiDocPreview succeeded [Detail] [Expand]
     Please click here to preview with your @microsoft account. 
    ️️✔️ azure-powershell succeeded [Detail] [Expand]
    • ️✔️Succeeded in generating from ed48a2b. 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.appplatform.DefaultTag [Preview SDK Changes]
      • Az.AppPlatform.0.1.0.nupkg
    ️❌ azure-sdk-for-python failed [Detail]
    • Code Generator Failed in generating from ed48a2b. 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] W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
      cmderr	[automation_init.sh] W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
      cmderr	[automation_init.sh] W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
      cmderr	[automation_init.sh] W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
      cmderr	[automation_init.sh] W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
      cmderr	[automation_init.sh] W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
      cmderr	[automation_init.sh] W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
      cmderr	[automation_init.sh] W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
      cmderr	[automation_init.sh] W: Target CNF (main/cnf/Commands-amd64) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
      cmderr	[automation_init.sh] W: Target CNF (main/cnf/Commands-all) is configured multiple times in /etc/apt/sources.list.d/azure-cli.list:1 and /etc/apt/sources.list.d/azure-cli.sources:1
      cmderr	[automation_init.sh] WARNING: Skipping azure-nspkg as it is not installed.
      cmderr	[automation_init.sh]
      cmderr	[automation_init.sh] npm notice New minor version of npm available! 10.5.0 -> 10.8.0
      cmderr	[automation_init.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.8.0>
      cmderr	[automation_init.sh] npm notice Run `npm install -g npm@10.8.0` to update!
      cmderr	[automation_init.sh] npm notice
      command	sh scripts/automation_generate.sh ../azure-sdk-for-python_tmp/generateInput.json ../azure-sdk-for-python_tmp/generateOutput.json
      cmdout	[automation_generate.sh] [Autorest] https://aka.ms/autorest
      cmdout	[automation_generate.sh] [Autorest]
      cmdout	[automation_generate.sh] [Autorest] There is a new version of AutoRest available (3.7.1).
      cmdout	[automation_generate.sh] [Autorest]  > You can install the newer version with with npm install -g autorest@latest
      cmdout	[automation_generate.sh] [Autorest]
      cmdout	[automation_generate.sh] [Autorest] info    |    Loading AutoRest core      '/home/cloudtest/.autorest/@autorestcore@3.10.2/nodemodules/@autorest/core/dist' (3.10.2)
      cmdout	[automation_generate.sh] [Autorest] error   | [OperationAbortedException] Error occurred. Exiting.
      cmdout	[automation_generate.sh] [Autorest] error   |   Error: [OperationAbortedException] Error occurred. Exiting.
      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] error   | literate/yaml-parsing-error | Syntax Error Encountered:  Syntax error: end of the stream or a document separator is expected
      cmdout	[automation_generate.sh] [Autorest]     - file:///mnt/vss/_work/1/s/azure-rest-api-specs/specification/appplatform/resource-manager/readme.python.md:64:1
      cmdout	[automation_generate.sh] [Autorest] error   | literate/yaml-parsing-error | Syntax Error Encountered:  Syntax error: end of the stream or a document separator is expected
      cmdout	[automation_generate.sh] [Autorest]     - file:///mnt/vss/_work/1/s/azure-rest-api-specs/specification/appplatform/resource-manager/readme.python.md:64:1
      cmdout	[automation_generate.sh] [Autorest] error   | literate/yaml-parsing-error | Syntax Error Encountered:  Syntax error: end of the stream or a document separator is expected
      cmdout	[automation_generate.sh] [Autorest]     - file:///mnt/vss/_work/1/s/azure-rest-api-specs/specification/appplatform/resource-manager/readme.python.md:72:1
      cmdout	[automation_generate.sh] [Autorest] error   | literate/yaml-parsing-error | Syntax Error Encountered:  Syntax error: end of the stream or a document separator is expected
      cmdout	[automation_generate.sh] [Autorest]     - file:///mnt/vss/_work/1/s/azure-rest-api-specs/specification/appplatform/resource-manager/readme.python.md:73:1
      cmdout	[automation_generate.sh] [Autorest] error   | literate/yaml-parsing-error | Syntax Error Encountered:  Syntax error: expected a single document in the stream, but found more
      cmdout	[automation_generate.sh] [Autorest]     - file:///mnt/vss/_work/1/s/azure-rest-api-specs/specification/appplatform/resource-manager/readme.python.md:63:1
      cmdout	[automation_generate.sh] [Autorest] fatal   | Failed to acquire 'require'd configuration 'file:///mnt/vss/_work/1/s/azure-rest-api-specs/specification/appplatform/resource-manager/readme.python.md'
      cmdout	[automation_generate.sh] [Autorest] https://aka.ms/autorest
      cmdout	[automation_generate.sh] [Autorest]
      cmdout	[automation_generate.sh] [Autorest] There is a new version of AutoRest available (3.7.1).
      cmdout	[automation_generate.sh] [Autorest]  > You can install the newer version with with npm install -g autorest@latest
      cmdout	[automation_generate.sh] [Autorest]
      cmdout	[automation_generate.sh] [Autorest] info    |    Loading AutoRest core      '/home/cloudtest/.autorest/@autorestcore@3.10.2/nodemodules/@autorest/core/dist' (3.10.2)
      cmdout	[automation_generate.sh] [Autorest] error   | [OperationAbortedException] Error occurred. Exiting.
      cmdout	[automation_generate.sh] [Autorest] error   |   Error: [OperationAbortedException] Error occurred. Exiting.
      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] error   | literate/yaml-parsing-error | Syntax Error Encountered:  Syntax error: end of the stream or a document separator is expected
      cmdout	[automation_generate.sh] [Autorest]     - file:///mnt/vss/_work/1/s/azure-rest-api-specs/specification/appplatform/resource-manager/readme.python.md:64:1
      cmdout	[automation_generate.sh] [Autorest] error   | literate/yaml-parsing-error | Syntax Error Encountered:  Syntax error: end of the stream or a document separator is expected
      cmdout	[automation_generate.sh] [Autorest]     - file:///mnt/vss/_work/1/s/azure-rest-api-specs/specification/appplatform/resource-manager/readme.python.md:64:1
      cmdout	[automation_generate.sh] [Autorest] error   | literate/yaml-parsing-error | Syntax Error Encountered:  Syntax error: end of the stream or a document separator is expected
      cmdout	[automation_generate.sh] [Autorest]     - file:///mnt/vss/_work/1/s/azure-rest-api-specs/specification/appplatform/resource-manager/readme.python.md:72:1
      cmdout	[automation_generate.sh] [Autorest] error   | literate/yaml-parsing-error | Syntax Error Encountered:  Syntax error: end of the stream or a document separator is expected
      cmdout	[automation_generate.sh] [Autorest]     - file:///mnt/vss/_work/1/s/azure-rest-api-specs/specification/appplatform/resource-manager/readme.python.md:73:1
      cmdout	[automation_generate.sh] [Autorest] error   | literate/yaml-parsing-error | Syntax Error Encountered:  Syntax error: expected a single document in the stream, but found more
      cmdout	[automation_generate.sh] [Autorest]     - file:///mnt/vss/_work/1/s/azure-rest-api-specs/specification/appplatform/resource-manager/readme.python.md:63:1
      cmdout	[automation_generate.sh] [Autorest] fatal   | Failed to acquire 'require'd configuration 'file:///mnt/vss/_work/1/s/azure-rest-api-specs/specification/appplatform/resource-manager/readme.python.md'
      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 warning [Detail]
    • ⚠️Warning in generating from ed48a2b. 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
      cmderr	[generate.py] [COMPILE] Maven build fail.
      cmderr	[generate.py] You can inquire in "Language - Java" Teams channel. Please include the link of this Pull Request in the query.
    • ️✔️azure-resourcemanager-appplatform-generated [Preview SDK Changes]
      • pom.xml
      • azure-resourcemanager-appplatform-generated-1.0.0-beta.1.jar
      • azure-resourcemanager-appplatform-generated-1.0.0-beta.1-sources.jar
    ️❌ azure-sdk-for-net-track2 failed [Detail]
    • Failed in generating from ed48a2b. SDK Automation 14.0.0
      command	pwsh ./eng/scripts/Automation-Sdk-Init.ps1 ../azure-sdk-for-net_tmp/initInput.json ../azure-sdk-for-net_tmp/initOutput.json
      command	pwsh ./eng/scripts/Invoke-GenerateAndBuildV2.ps1 ../azure-sdk-for-net_tmp/generateInput.json ../azure-sdk-for-net_tmp/generateOutput.json
      cmderr	[Invoke-GenerateAndBuildV2.ps1] GeneratePackage: /mnt/vss/_work/1/s/azure-sdk-for-net/eng/scripts/automation/GenerateAndBuildLib.ps1:714
      cmderr	[Invoke-GenerateAndBuildV2.ps1] Line |
      cmderr	[Invoke-GenerateAndBuildV2.ps1]  714 |          GeneratePackage -projectFolder $projectFolder -sdkRootPath $s …
      cmderr	[Invoke-GenerateAndBuildV2.ps1]      |          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      cmderr	[Invoke-GenerateAndBuildV2.ps1]      | Failed to generate sdk. exit code: False
      cmderr	[Invoke-GenerateAndBuildV2.ps1] Get-ChildItem: /mnt/vss/_work/1/s/azure-sdk-for-net/eng/scripts/automation/GenerateAndBuildLib.ps1:807
      cmderr	[Invoke-GenerateAndBuildV2.ps1] Line |
      cmderr	[Invoke-GenerateAndBuildV2.ps1]  807 |  … rtifacts += Get-ChildItem $artifactsPath -Filter *.nupkg -exclude *.s …
      cmderr	[Invoke-GenerateAndBuildV2.ps1]      |                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      cmderr	[Invoke-GenerateAndBuildV2.ps1]      | Cannot find path
      cmderr	[Invoke-GenerateAndBuildV2.ps1]      | '/mnt/vss/_work/1/s/azure-sdk-for-net/artifacts/packages/Debug/' because
      cmderr	[Invoke-GenerateAndBuildV2.ps1]      | it does not exist.
      cmderr	[Invoke-GenerateAndBuildV2.ps1] GeneratePackage: /mnt/vss/_work/1/s/azure-sdk-for-net/eng/scripts/automation/GenerateAndBuildLib.ps1:714
      cmderr	[Invoke-GenerateAndBuildV2.ps1] Line |
      cmderr	[Invoke-GenerateAndBuildV2.ps1]  714 |          GeneratePackage -projectFolder $projectFolder -sdkRootPath $s …
      cmderr	[Invoke-GenerateAndBuildV2.ps1]      |          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      cmderr	[Invoke-GenerateAndBuildV2.ps1]      | Failed to generate sdk artifact
    • Azure.ResourceManager.AppPlatform [Preview SDK Changes]
      info	[Changelog]
    ️️✔️ azure-sdk-for-js succeeded [Detail] [Expand]
    • ️✔️Succeeded in generating from ed48a2b. 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
    • ️✔️@azure/arm-appplatform [Preview SDK Changes]
      • azure-arm-appplatform-3.1.0-beta.1.tgz
    ️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]
    • ️✔️Succeeded in generating from ed48a2b. 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
    • ️✔️sdk/resourcemanager/appplatform/armappplatform [Preview SDK Changes]
    ️❌ azure-resource-manager-schemas failed [Detail]
    • Code Generator Failed in generating from ed48a2b. Schema Automation 14.0.0
      command	.sdkauto/initScript.sh ../azure-resource-manager-schemas_tmp/initInput.json ../azure-resource-manager-schemas_tmp/initOutput.json
      cmderr	[initScript.sh] Submodule 'bicep-types-az' (https://github.com/Azure/bicep-types-az) registered for path 'bicep-types-az'
      cmderr	[initScript.sh] Cloning into '/mnt/vss/_work/1/s/azure-resource-manager-schemas/bicep-types-az'...
      cmderr	[initScript.sh] Submodule 'bicep-types' (https://github.com/Azure/bicep-types) registered for path 'bicep-types-az/bicep-types'
      cmderr	[initScript.sh] Cloning into '/mnt/vss/_work/1/s/azure-resource-manager-schemas/bicep-types-az/bicep-types'...
      cmderr	[initScript.sh]  notice
      cmderr	[initScript.sh] npm notice New minor version of npm available! 10.5.0 -> 10.8.0
      cmderr	[initScript.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.8.0>
      cmderr	[initScript.sh] npm notice Run `npm install -g npm@10.8.0` to update!
      cmderr	[initScript.sh] npm notice
      error	Script return with result [failed] code [1] signal [null] cwd [azure-resource-manager-schemas]: .sdkauto/initScript.sh
      warn	File azure-resource-manager-schemas_tmp/initOutput.json not found to read
      command	.sdkauto/generateScript.sh ../azure-resource-manager-schemas_tmp/generateInput.json ../azure-resource-manager-schemas_tmp/generateOutput.json
      cmderr	[generateScript.sh] /mnt/vss/_work/1/a/unified-pipeline-runtime/common/temp/node_modules/.pnpm/ts-node@9.0.0_typescript@5.3.3/node_modules/ts-node/src/index.ts:500
      cmderr	[generateScript.sh]     return new TSError(diagnosticText, diagnosticCodes)
      cmderr	[generateScript.sh]            ^
      cmderr	[generateScript.sh] TSError: ⨯ Unable to compile TypeScript:
      cmderr	[generateScript.sh] cmd/generateall.ts(6,20): error TS2307: Cannot find module 'colors' or its corresponding type declarations.
      cmderr	[generateScript.sh] cmd/generateall.ts(10,19): error TS2307: Cannot find module 'yargs' or its corresponding type declarations.
      cmderr	[generateScript.sh] cmd/generateall.ts(11,18): error TS2307: Cannot find module 'path' or its corresponding type declarations.
      cmderr	[generateScript.sh] cmd/generateall.ts(13,35): error TS2307: Cannot find module 'fs' or its corresponding type declarations.
      cmderr	[generateScript.sh] cmd/generateall.ts(14,23): error TS2307: Cannot find module 'strip-ansi' or its corresponding type declarations.
      cmderr	[generateScript.sh] cmd/generateall.ts(42,9): error TS2584: Cannot find name 'console'. Do you need to change your target library? Try changing the 'lib' compiler option to include 'dom'.
      cmderr	[generateScript.sh] cmd/generateall.ts(53,9): error TS2584: Cannot find name 'console'. Do you need to change your target library? Try changing the 'lib' compiler option to include 'dom'.
      cmderr	[generateScript.sh] cmd/generateall.ts(69,67): error TS7006: Parameter 'x' implicitly has an 'any' type.
      cmderr	[generateScript.sh] cmd/generateall.ts(70,49): error TS7006: Parameter 'f' implicitly has an 'any' type.
      cmderr	[generateScript.sh] cmd/generateall.ts(94,21): error TS2584: Cannot find name 'console'. Do you need to change your target library? Try changing the 'lib' compiler option to include 'dom'.
      cmderr	[generateScript.sh] cmd/generateall.ts(105,21): error TS2584: Cannot find name 'console'. Do you need to change your target library? Try changing the 'lib' compiler option to include 'dom'.
      cmderr	[generateScript.sh] cmd/generateall.ts(106,21): error TS2584: Cannot find name 'console'. Do you need to change your target library? Try changing the 'lib' compiler option to include 'dom'.
      cmderr	[generateScript.sh] cmd/generateall.ts(157,13): error TS2591: Cannot find name 'process'. Do you need to install type definitions for node? Try `npm i --save-dev @types/node` and then add 'node' to the types field in your tsconfig.
      cmderr	[generateScript.sh]     at createTSError (/mnt/vss/_work/1/a/unified-pipeline-runtime/common/temp/node_modules/.pnpm/ts-node@9.0.0_typescript@5.3.3/node_modules/ts-node/src/index.ts:500:12)
      cmderr	[generateScript.sh]     at reportTSError (/mnt/vss/_work/1/a/unified-pipeline-runtime/common/temp/node_modules/.pnpm/ts-node@9.0.0_typescript@5.3.3/node_modules/ts-node/src/index.ts:504:19)
      cmderr	[generateScript.sh]     at getOutput (/mnt/vss/_work/1/a/unified-pipeline-runtime/common/temp/node_modules/.pnpm/ts-node@9.0.0_typescript@5.3.3/node_modules/ts-node/src/index.ts:739:36)
      cmderr	[generateScript.sh]     at Object.compile (/mnt/vss/_work/1/a/unified-pipeline-runtime/common/temp/node_modules/.pnpm/ts-node@9.0.0_typescript@5.3.3/node_modules/ts-node/src/index.ts:955:32)
      cmderr	[generateScript.sh]     at Module.m._compile (/mnt/vss/_work/1/a/unified-pipeline-runtime/common/temp/node_modules/.pnpm/ts-node@9.0.0_typescript@5.3.3/node_modules/ts-node/src/index.ts:1043:43)
      cmderr	[generateScript.sh]     at Module._extensions..js (node:internal/modules/cjs/loader:1422:10)
      cmderr	[generateScript.sh]     at Object.require.extensions.<computed> [as .ts] (/mnt/vss/_work/1/a/unified-pipeline-runtime/common/temp/node_modules/.pnpm/ts-node@9.0.0_typescript@5.3.3/node_modules/ts-node/src/index.ts:1046:12)
      cmderr	[generateScript.sh]     at Module.load (node:internal/modules/cjs/loader:1203:32)
      cmderr	[generateScript.sh]     at Function.Module._load (node:internal/modules/cjs/loader:1019:12)
      cmderr	[generateScript.sh]     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12)
      error	Script return with result [failed] code [1] signal [null] cwd [azure-resource-manager-schemas]: .sdkauto/generateScript.sh
      warn	Skip package processing as generation is failed
      error	ERROR: The 'breakingChangesLabel' configuration is missing or incorrect from the 'swagger_to_sdk_config.json file.
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-workflow-bot openapi-workflow-bot bot added ShiftLeftViolation DoNotMerge <valid label in PR review process> use to hold merge after approval labels May 21, 2024
    @AzureRestAPISpecReview AzureRestAPISpecReview added the ReadyForApiTest <valid label in PR review process>add this label when swagger and service APIs are ready for test label May 22, 2024
    @smile37773
    Copy link
    Member Author

    Close pull request

    @smile37773 smile37773 closed this May 30, 2024
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    ARMReview DoNotMerge <valid label in PR review process> use to hold merge after approval new-api-version ReadyForApiTest <valid label in PR review process>add this label when swagger and service APIs are ready for test resource-manager ShiftLeftViolation WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    None yet

    3 participants