Skip to content

Cadl use latest codegen #21689

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

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from
Draft

Cadl use latest codegen #21689

wants to merge 6 commits into from

Conversation

dw511214992
Copy link
Member

@dw511214992 dw511214992 commented Nov 29, 2022

Data Plane API - Pull Request

API Info: The Basics

Most of the information about your service should be captured in the issue that serves as your engagement record.

  • Link to engagement record issue:

Is this review for (select one):

  • a private preview
  • a public preview
  • GA release

Change Scope

This section will help us focus on the specific parts of your API that are new or have been modified.
Please share a link to the design document for the new APIs, a link to the previous Open API document (swagger) if applicable, and the root paths that have been updated.

  • Design Document:
  • Previous Open API Doc:
  • Updated paths:

❔Got questions? Need additional info?? We are here to help!

Contact us!

The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

Click here for links to tools, specs, guidelines & other good stuff

Tooling

Guidelines & Specifications

Helpful Links

@openapi-workflow-bot
Copy link

Hi, @dw511214992 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]

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Nov 29, 2022

    Swagger Validation Report

    ️️✔️BreakingChange succeeded [Detail] [Expand]
    There are no breaking changes.
    ️❌Breaking Change(Cross-Version): 2 Errors, 0 Warnings failed [Detail] The following breaking changes are detected by comparison with the latest stable version:
    Rule Message
    Runtime Exception "new":"https://github.com/Azure/azure-rest-api-specs/blob/c27b986cc74bf0e468246f9e20b80437767680c9/specification/confidentialledger/data-plane/Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json",
    "old":"https://github.com/Azure/azure-rest-api-specs/blob/main/specification/confidentialledger/data-plane/Microsoft.ConfidentialLedger/stable/2022-05-13/confidentialledger.json",
    "details":"Command failed: node /mnt/vss/_work/_tasks/AzureApiValidation_5654d05d-82c1-48da-ad8f-161b817f6d41/0.0.46/common/temp/node_modules/.pnpm/@Azure[email protected]/node_modules/autorest/dist/app.js --v2 --input-file=specification/confidentialledger/data-plane/Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json --output-artifact=swagger-document.json --output-artifact=swagger-document.map --output-file=new --output-folder=/tmp\nERROR: Schema violation: Data does not match any schemas from 'oneOf'\n - file:///mnt/vss/_work/1/azure-rest-api-specs/specification/confidentialledger/data-plane/Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json:41:4 ($.securityDefinitions.OAuth2Auth)\nFATAL: swagger-document/individual/schema-validator - FAILED\nFATAL: Error: [OperationAbortedException] Error occurred. Exiting.\nProcess() cancelled due to exception : [OperationAbortedException] Error occurred. Exiting.\n"


    The following breaking changes are detected by comparison with the latest preview version:

    Rule Message
    Runtime Exception "new":"https://github.com/Azure/azure-rest-api-specs/blob/c27b986cc74bf0e468246f9e20b80437767680c9/specification/confidentialledger/data-plane/Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json",
    "old":"https://github.com/Azure/azure-rest-api-specs/blob/main/specification/confidentialledger/data-plane/Microsoft.ConfidentialLedger/preview/0.1-preview/confidentialledger.json",
    "details":"Command failed: node /mnt/vss/_work/_tasks/AzureApiValidation_5654d05d-82c1-48da-ad8f-161b817f6d41/0.0.46/common/temp/node_modules/.pnpm/@Azure[email protected]/node_modules/autorest/dist/app.js --v2 --input-file=specification/confidentialledger/data-plane/Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json --output-artifact=swagger-document.json --output-artifact=swagger-document.map --output-file=new --output-folder=/tmp\nERROR: Schema violation: Data does not match any schemas from 'oneOf'\n - file:///mnt/vss/_work/1/azure-rest-api-specs/specification/confidentialledger/data-plane/Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json:41:4 ($.securityDefinitions.OAuth2Auth)\nFATAL: swagger-document/individual/schema-validator - FAILED\nFATAL: Error: [OperationAbortedException] Error occurred. Exiting.\nProcess() cancelled due to exception : [OperationAbortedException] Error occurred. Exiting.\n"
    ️️✔️CredScan succeeded [Detail] [Expand]
    There is no credential detected.
    ️❌LintDiff: 6 Errors, 53 Warnings failed [Detail]
    compared tags (via openapi-validator v2.0.0) new version base version
    package-2022-08-13 package-2022-08-13(c27b986) default(main)

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

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

    Rule Message Related RPC [For API reviewers]
    AvoidAnonymousParameter Inline/anonymous models must not be used, instead define a schema with a model name in the 'definitions' section and refer to it. This allows operations to share the models.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L195
    AvoidAnonymousParameter Inline/anonymous models must not be used, instead define a schema with a model name in the 'definitions' section and refer to it. This allows operations to share the models.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L415
    AvoidAnonymousTypes Inline/anonymous models must not be used, instead define a schema with a model name in the 'definitions' section and refer to it. This allows operations to share the models.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L431
    AvoidAnonymousTypes Inline/anonymous models must not be used, instead define a schema with a model name in the 'definitions' section and refer to it. This allows operations to share the models.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L453
    RequiredReadOnlyProperties Property 'collectionId' is a required property. It should not be marked as 'readonly'
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L566
    RequiredReadOnlyProperties Property 'transactionId' is a required property. It should not be marked as 'readonly'
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L566
    ⚠️ SecurityDefinitionDescription Security definition should have a description.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L41
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L54
    ⚠️ ErrorResponse Error response should contain a x-ms-error-code header.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L75
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L85
    ⚠️ SuccessResponseBody All success responses except 202 & 204 should define a response body.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L95
    ⚠️ ErrorResponse Error response should contain a x-ms-error-code header.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L98
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L108
    ⚠️ SuccessResponseBody All success responses except 202 & 204 should define a response body.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L118
    ⚠️ ErrorResponse Error response should contain a x-ms-error-code header.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L121
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L131
    ⚠️ SuccessResponseBody All success responses except 202 & 204 should define a response body.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L141
    ⚠️ ErrorResponse Error response should contain a x-ms-error-code header.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L144
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L154
    ⚠️ PaginationResponse Response body schema of pageable response should contain top-level array property value
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L166
    ⚠️ ErrorResponse Error response should contain a x-ms-error-code header.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L170
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L181
    ⚠️ ParameterDescription Parameter should have a description.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L192
    ⚠️ RequestBodyOptional The body parameter is not marked as required.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L192
    ⚠️ Post201Response Using post for a create operation is discouraged.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L212
    ⚠️ SuccessResponseBody All success responses except 202 & 204 should define a response body.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L212
    ⚠️ ErrorResponse Error response should contain a x-ms-error-code header.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L221
    ⚠️ XmsExamplesRequired Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L231
    ⚠️ PathParameterSchema Path parameter should specify a maximum length (maxLength) and characters allowed (pattern).
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L236
    ⚠️ ErrorResponse Error response should contain a x-ms-error-code header.
    Location: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L253
    ️❌Avocado: 1 Errors, 0 Warnings failed [Detail]
    Rule Message
    MISSING_README Can not find readme.md in the folder. If no readme.md file, it will block SDK generation.
    folder: c27b986cc74bf0e468246f9e20b80437767680c9/specification/confidentialledger/ConfientialLedger
    ️️✔️ApiReadinessCheck succeeded [Detail] [Expand]
    ️⚠️~[Staging] ServiceAPIReadinessTest: 0 Warnings warning [Detail]

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

    ️️✔️~[Staging] SwaggerAPIView succeeded [Detail] [Expand]
    ️❌ModelValidation: 13 Errors, 0 Warnings failed [Detail]
    Rule Message
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in ConfidentialLedger_ListCollections.
    Url: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L54:14
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in ConfidentialLedger_GetEnclaveQuotes.
    Url: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L85:14
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in ConfidentialLedger_GetConstitution.
    Url: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L108:14
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in ConfidentialLedger_GetConsortiumMembers.
    Url: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L131:14
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in ConfidentialLedger_ListLedgerEntries.
    Url: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L154:14
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in ConfidentialLedger_CreateLedgerEntry.
    Url: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L181:15
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in ConfidentialLedger_GetLedgerEntry.
    Url: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L231:14
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in ConfidentialLedger_GetReceipt.
    Url: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L263:14
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in ConfidentialLedger_GetTransactionStatus.
    Url: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L292:14
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in ConfidentialLedger_GetCurrentLedgerEntry.
    Url: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L321:14
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in ConfidentialLedger_DeleteUser.
    Url: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L350:17
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in ConfidentialLedger_GetUser.
    Url: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L374:14
    XMS_EXAMPLE_NOTFOUND_ERROR x-ms-example not found in ConfidentialLedger_CreateOrUpdateUser.
    Url: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L401:16
    ️❌SemanticValidation: 19 Errors, 0 Warnings failed [Detail]
    Rule Message
    OBJECT_ADDITIONAL_PROPERTIES Additional properties not allowed: flow
    JsonUrl: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L43:15
    OBJECT_ADDITIONAL_PROPERTIES Additional properties not allowed: authorizationUrl
    JsonUrl: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L43:15
    OBJECT_ADDITIONAL_PROPERTIES Additional properties not allowed: tokenUrl
    JsonUrl: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L43:15
    OBJECT_ADDITIONAL_PROPERTIES Additional properties not allowed: scopes
    JsonUrl: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L43:15
    ENUM_MISMATCH No enum match for: oauth2
    JsonUrl: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L43:15
    OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: name
    JsonUrl: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L43:15
    OBJECT_MISSING_REQUIRED_PROPERTY Missing required property: in
    JsonUrl: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L43:15
    OBJECT_ADDITIONAL_PROPERTIES Additional properties not allowed: flow
    JsonUrl: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L43:15
    OBJECT_ADDITIONAL_PROPERTIES Additional properties not allowed: authorizationUrl
    JsonUrl: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L43:15
    OBJECT_ADDITIONAL_PROPERTIES Additional properties not allowed: tokenUrl
    JsonUrl: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L43:15
    OBJECT_ADDITIONAL_PROPERTIES Additional properties not allowed: scopes
    JsonUrl: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L43:15
    ENUM_MISMATCH No enum match for: oauth2
    JsonUrl: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L43:15
    OBJECT_ADDITIONAL_PROPERTIES Additional properties not allowed: tokenUrl
    JsonUrl: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L43:15
    OBJECT_ADDITIONAL_PROPERTIES Additional properties not allowed: authorizationUrl
    JsonUrl: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L43:15
    ENUM_MISMATCH No enum match for: implicit
    JsonUrl: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L43:15
    OBJECT_ADDITIONAL_PROPERTIES Additional properties not allowed: authorizationUrl
    JsonUrl: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L43:15
    ENUM_MISMATCH No enum match for: implicit
    JsonUrl: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L43:15
    ENUM_MISMATCH No enum match for: implicit
    JsonUrl: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L43:15
    ONE_OF_MISSING Data does not match any schemas from 'oneOf'
    JsonUrl: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L43:15
    ️️✔️PoliCheck succeeded [Detail] [Expand]
    Validation passed for PoliCheck.
    ️️✔️PrettierCheck succeeded [Detail] [Expand]
    Validation passes for PrettierCheck.
    ️❌SpellCheck: 3 Errors, 0 Warnings failed [Detail]
    Rule Message
    HowToFix Unknown word (updateable), please fix the error or add words to ./custom-words.txt
    path: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L203:55
    HowToFix Unknown word (Updateable), please fix the error or add words to ./custom-words.txt
    path: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L207:31
    HowToFix Unknown word (Updateable), please fix the error or add words to ./custom-words.txt
    path: Microsoft.ConfidentialLedger/stable/2022-08-13/confidentialledger.json#L424:50
    ️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
    Validation passes for Lint(RPaaS).
    ️❌CadlValidation: 2 Errors, 2 Warnings failed [Detail]
    Rule Message
    MissingExamplesDirectory "details":"The 'examples' directory is missing in the cadl folder specification/confidentialledger/ConfientialLedger,
    please ensure the 'examples' is added in the PR."
    SwaggerNotExistInPR "details":"the generated swagger file openapi.json from cadl specification/confidentialledger/ConfientialLedger is not in the PR,
    please make sure it presents into the PR."
    ⚠️ MissingCadlProjectConfig "details":"The configuration 'output-file' for '@azure-tools/cadl-autorest' is missing in the cadl-project.yaml under folder specification/confidentialledger/ConfientialLedger,
    please ensure it is added in the configuration of the emitter '@azure-tools/cadl-autorest'."
    ⚠️ MissingCadlProjectConfig "details":"The configuration 'azure-resource-provider-folder' for '@azure-tools/cadl-autorest' is missing in the cadl-project.yaml under folder specification/confidentialledger/ConfientialLedger,
    please ensure it is added in the configuration of the emitter '@azure-tools/cadl-autorest'."
    ️️✔️PR Summary succeeded [Detail] [Expand]
    Validation passes for Summary.
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Nov 29, 2022

    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 warning [Detail]
    • ⚠️Warning [Logs] Generate from b77c1561cd1ab25080b41455ba3b52a0db4142f6. 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.
      warn		specification/confidentialledger/data-plane/readme.md skipped due to azure-sdk-for-python not found in swagger-to-sdk
      command	sh scripts/automation_generate.sh ../azure-sdk-for-python_tmp/generateInput.json ../azure-sdk-for-python_tmp/generateOutput.json
      cmderr	[automation_generate.sh] npm notice
      cmderr	[automation_generate.sh] npm notice New major version of npm available! 8.19.2 -> 9.1.2
      cmderr	[automation_generate.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.1.2>
      cmderr	[automation_generate.sh] npm notice Run `npm install -g [email protected]` to update!
      cmderr	[automation_generate.sh] npm notice
    • ️✔️azure-security-confidentialledgerbugbash [View full logs]  [Preview SDK Changes]
      info	[Changelog] data-plan skip changelog generation temporarily
    ️⚠️ azure-sdk-for-net-track2 warning [Detail]
    • ⚠️Warning [Logs] Generate from b77c1561cd1ab25080b41455ba3b52a0db4142f6. 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
      warn		specification/confidentialledger/data-plane/readme.md skipped due to azure-sdk-for-net-track2 not found in swagger-to-sdk
      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] npm notice
      cmderr	[Invoke-GenerateAndBuildV2.ps1] npm notice New major version of npm available! 8.15.0 -> 9.1.2
      cmderr	[Invoke-GenerateAndBuildV2.ps1] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.1.2>
      cmderr	[Invoke-GenerateAndBuildV2.ps1] npm notice Run `npm install -g [email protected]` to update!
      cmderr	[Invoke-GenerateAndBuildV2.ps1] npm notice
    • ️✔️Azure.Security.ConfidentialLedgerBugBash [View full logs]  [Preview SDK Changes]
      info	[Changelog]
    ️️✔️ azure-sdk-for-js succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs] Generate from b77c1561cd1ab25080b41455ba3b52a0db4142f6. 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
      warn		specification/confidentialledger/data-plane/readme.md skipped due to azure-sdk-for-js not found in swagger-to-sdk
      command	sh .scripts/automation_generate.sh ../azure-sdk-for-js_tmp/generateInput.json ../azure-sdk-for-js_tmp/generateOutput.json
    • ️✔️@azure-rest/confidentialledger-bugbash [View full logs]  [Preview SDK Changes]
      info	[Changelog]
      error	breakingChangeTracking is enabled, but version or changelogItem is not found in output.
    ️⚠️ azure-sdk-for-java warning [Detail]
    • ⚠️Warning [Logs] Generate from b77c1561cd1ab25080b41455ba3b52a0db4142f6. 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
      cmderr	[init.sh] [notice] A new release of pip available: 22.3 -> 22.3.1
      cmderr	[init.sh] [notice] To update, run: pip install --upgrade pip
      cmderr	[init.sh] [notice] A new release of pip available: 22.3 -> 22.3.1
      cmderr	[init.sh] [notice] To update, run: pip install --upgrade pip
      warn		specification/confidentialledger/data-plane/readme.md skipped due to azure-sdk-for-java not found in swagger-to-sdk
      command	./eng/mgmt/automation/generate.py ../azure-sdk-for-java_tmp/generateInput.json ../azure-sdk-for-java_tmp/generateOutput.json
      cmderr	[generate.py] npm notice
      cmderr	[generate.py] npm notice New major version of npm available! 8.15.0 -> 9.1.2
      cmderr	[generate.py] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.1.2>
      cmderr	[generate.py] npm notice Run `npm install -g [email protected]` to update!
      cmderr	[generate.py] npm notice
    • ️✔️azure-confidentialledgerbugbash [View full logs]  [Preview SDK Changes]
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Nov 29, 2022

    Generated ApiView

    Language Package Name ApiView Link
    swagger Microsoft.ConfidentialLedger https://apiview.dev/Assemblies/Review/39c76e5ae82c49b7a12f858b67d6b4ab
    Python azure-security-confidentialledgerbugbash https://apiview.dev/Assemblies/Review/b51163c01c7a4b4d860cb3a8f9996fbf
    .Net Azure.Security.ConfidentialLedgerBugBash https://apiview.dev/Assemblies/Review/feda7c9e47fa42389dab9c99d40e8cb1
    JavaScript @azure-rest/confidentialledger-bugbash https://apiview.dev/Assemblies/Review/dc7ecbd266304325af1ddf9c690bd6bb
    Java azure-confidentialledgerbugbash https://apiview.dev/Assemblies/Review/174b2a796d0649bcbfeef1ad13966753

    @dw511214992
    Copy link
    Member Author

    /azp run

    1 similar comment
    @dw511214992
    Copy link
    Member Author

    /azp run

    @azure-pipelines
    Copy link

    Azure Pipelines successfully started running 1 pipeline(s).

    @dw511214992
    Copy link
    Member Author

    /azp run

    @azure-pipelines
    Copy link

    Azure Pipelines successfully started running 1 pipeline(s).

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    APIStewardshipBoard-SignedOff The Azure API Stewardship team has reviewed and approved the changes. Cadl Authored with Cadl data-plane
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    3 participants