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

Feature/gallery 220303 72 #20296

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

Feature/gallery 220303 72 #20296

wants to merge 3 commits into from

Conversation

Sandido
Copy link
Member

@Sandido Sandido commented Aug 18, 2022

Trying common.json with version 1.0.

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

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo. If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.

Changelog

Add a changelog entry for this PR by answering the following questions:

  1. What's the purpose of the update?
    • new service onboarding
    • new API version
    • update existing version for new feature
    • update existing version to fix swagger quality issue in s360
    • Other, please clarify
  2. When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
  3. When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
  4. If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.
    • SDK of .NET (need service team to ensure code readiness)
    • SDK of Python
    • SDK of Java
    • SDK of Js
    • SDK of Go
    • PowerShell
    • CLI
    • Terraform
    • No refresh required for updates in this PR

Contribution checklist:

If any further question about AME onboarding or validation tools, please view the FAQ.

ARM API Review Checklist

Applicability: ⚠️

If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

  • Change to data plane APIs
  • Adding new properties
  • All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

  • Check this box if any of the following appy to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

    • Adding a new service
    • Adding new API(s)
    • Adding a new API version
      -[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.
  • Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

  • If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist

If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

  • Removing API(s) in a stable version
  • Removing properties in a stable version
  • Removing API version(s) in a stable version
  • Updating API in a stable or public preview version with Breaking Change Validation errors
  • Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

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.

Please follow the link to find more details on PR review process.

readme only

lower case ech

from v1 to actual version
@openapi-workflow-bot
Copy link

Hi, @Sandido 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. vscswagger@microsoft.com

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Aug 18, 2022

    Swagger Validation Report

    ️️✔️BreakingChange succeeded [Detail] [Expand]
    There are no breaking changes.
    ️⚠️Breaking Change(Cross-Version): 3 Warnings warning [Detail]
    compared swaggers (via Oad v0.9.7)] new version base version
    communityGallery.json 2022-03-03(b8ddcda) 2022-01-03(main)
    gallery.json 2022-03-03(b8ddcda) 2022-01-03(main)
    gallery.json 2022-03-03(b8ddcda) 2020-09-30(main)
    galleryRPCommon.json 2022-03-03(b8ddcda) 2022-01-03(main)
    sharedGallery.json 2022-03-03(b8ddcda) 2022-01-03(main)
    sharedGallery.json 2022-03-03(b8ddcda) 2020-09-30(main)

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

    Rule Message
    ⚠️ 1007 - RemovedClientParameter The new version is missing a client parameter that was found in the old version. Was 'LocationNameParamter' removed or renamed?
    New: azure-rest-api-specs/blob/b8ddcdae06befb2a54babbea6f6b9856af5b74cb/revision#L1024:2
    Old: GalleryRP/preview/2020-09-30/sharedGallery.json#L762:3
    ⚠️ 1026 - TypeChanged The new version has a different type 'object' than the previous one ''.
    New: galleryRP/stable/2022-03-03/gallery.json#L2491:9
    Old: GalleryRP/preview/2020-09-30/gallery.json#L2358:9
    ⚠️ 1026 - TypeChanged The new version has a different type 'object' than the previous one ''.
    New: galleryRP/stable/2022-03-03/gallery.json#L2507:5
    Old: GalleryRP/preview/2020-09-30/gallery.json#L2371:5
    ️️✔️CredScan succeeded [Detail] [Expand]
    There is no credential detected.
    ️❌LintDiff: 1 Errors, 0 Warnings failed [Detail]
    compared tags (via openapi-validator v1.13.0) new version base version
    package-2022-03-03 package-2022-03-03(b8ddcda) default(main)

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

    Rule Message Related RPC [For API reviewers]
    R3012 - APIVersionPattern API Version must be in the format: yyyy-MM-dd, optionally followed by -preview, -alpha, -beta, -rc, -privatepreview.
    Location: Microsoft.Compute/common-types/v1/common.json#L6


    The following errors/warnings exist before current PR submission:

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

    Rule Message
    R4037 - MissingTypeObject The schema 'ApiErrorBase' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Compute/common-types/v1/common.json#L38
    R4037 - MissingTypeObject The schema 'ApiErrorBase' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Compute/common-types/v1/common.json#L38
    R4037 - MissingTypeObject The schema 'ApiErrorBase' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Compute/common-types/v1/common.json#L38
    R4037 - MissingTypeObject The schema 'ApiErrorBase' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Compute/common-types/v1/common.json#L38
    R4037 - MissingTypeObject The schema 'InnerError' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Compute/common-types/v1/common.json#L55
    R4037 - MissingTypeObject The schema 'InnerError' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Compute/common-types/v1/common.json#L55
    R4037 - MissingTypeObject The schema 'InnerError' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Compute/common-types/v1/common.json#L55
    R4037 - MissingTypeObject The schema 'InnerError' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Compute/common-types/v1/common.json#L55
    R4037 - MissingTypeObject The schema 'CloudError' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Compute/common-types/v1/common.json#L68
    R4037 - MissingTypeObject The schema 'CloudError' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Compute/common-types/v1/common.json#L68
    R4037 - MissingTypeObject The schema 'CloudError' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Compute/common-types/v1/common.json#L68
    R4037 - MissingTypeObject The schema 'CloudError' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Compute/common-types/v1/common.json#L68
    R4037 - MissingTypeObject The schema 'ApiError' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Compute/common-types/v1/common.json#L77
    R4037 - MissingTypeObject The schema 'ApiError' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Compute/common-types/v1/common.json#L77
    R4037 - MissingTypeObject The schema 'ApiError' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Compute/common-types/v1/common.json#L77
    R4037 - MissingTypeObject The schema 'ApiError' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Compute/common-types/v1/common.json#L77
    R4037 - MissingTypeObject The schema 'Resource' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Compute/common-types/v1/common.json#L109
    R4037 - MissingTypeObject The schema 'Resource' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Compute/common-types/v1/common.json#L109
    R4037 - MissingTypeObject The schema 'SubResource' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Compute/common-types/v1/common.json#L144
    R4037 - MissingTypeObject The schema 'SubResourceReadOnly' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Compute/common-types/v1/common.json#L153
    R4037 - MissingTypeObject The schema 'ExtendedLocation' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: Microsoft.Compute/common-types/v1/common.json#L207
    R4037 - MissingTypeObject The schema 'PirCommunityGalleryResource' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: galleryRP/stable/2022-03-03/communityGallery.json#L267
    R4037 - MissingTypeObject The schema 'CommunityGalleryIdentifier' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: galleryRP/stable/2022-03-03/communityGallery.json#L291
    R4037 - MissingTypeObject The schema 'CommunityGallery' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: galleryRP/stable/2022-03-03/communityGallery.json#L300
    R4037 - MissingTypeObject The schema 'CommunityGalleryImage' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: galleryRP/stable/2022-03-03/communityGallery.json#L330
    R4037 - MissingTypeObject The schema 'CommunityGalleryImageProperties' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: galleryRP/stable/2022-03-03/communityGallery.json#L344
    R4037 - MissingTypeObject The schema 'CommunityGalleryImageVersion' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: galleryRP/stable/2022-03-03/communityGallery.json#L449
    R4037 - MissingTypeObject The schema 'CommunityGalleryImageVersionProperties' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: galleryRP/stable/2022-03-03/communityGallery.json#L463
    R4037 - MissingTypeObject The schema 'Gallery' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: galleryRP/stable/2022-03-03/gallery.json#L1735
    R4037 - MissingTypeObject The schema 'GalleryUpdate' is considered an object but without a 'type:object', please add the missing 'type:object'.
    Location: galleryRP/stable/2022-03-03/gallery.json#L1749
    ️⚠️Avocado: 1 Warnings warning [Detail]
    Rule Message
    ⚠️ MULTIPLE_API_VERSION The default tag contains multiple API versions swaggers.
    readme: specification/compute/resource-manager/readme.md
    tag: specification/compute/resource-manager/readme.md#tag-package-2022-03-03
    ️️✔️ApiReadinessCheck succeeded [Detail] [Expand]
    ️❌~[Staging] ServiceAPIReadinessTest: 0 Errors, 0 Warnings failed [Detail] Service API Readiness Test failed. Check pipeline artifact for detail report.
    ️️✔️ModelValidation succeeded [Detail] [Expand]
    Validation passes for ModelValidation.
    ️️✔️SemanticValidation succeeded [Detail] [Expand]
    Validation passes for SemanticValidation.
    ️️✔️PoliCheck succeeded [Detail] [Expand]
    Validation passed for PoliCheck.
    ️❌SDK Track2 Validation: 2 Errors, 1 Warnings failed [Detail]
    • The following tags are being changed in this PR
      • "https://github.com/Azure/azure-rest-api-specs/blob/b8ddcdae06befb2a54babbea6f6b9856af5b74cb/specification/compute/resource-manager/readme.md#tag-package-2022-03-03">compute/resource-manager/readme.md#package-2022-03-03
      • "https://github.com/Azure/azure-rest-api-specs/blob/b8ddcdae06befb2a54babbea6f6b9856af5b74cb/specification/compute/resource-manager/readme.md#tag-package-2022-03-03-only">compute/resource-manager/readme.md#package-2022-03-03-only
    The following errors/warnings are introduced by current PR:
    Rule Message
    PreCheck/DuplicateSchema "readme":"compute/resource-manager/readme.md",
    "tag":"package-2022-03-03",
    "details":"Duplicate Schema named 'PurchasePlan' (1 differences):\n - properties.promotionCode: => "$ref":"#/components/schemas/schemas:1443",
    "description":"The Offer Promotion Code."; This error can be temporarily avoided by using the 'modelerfour.lenient-model-deduplication' setting. NOTE: This setting will be removed in a future version of @autorest/modelerfour; schemas should be updated to fix this issue sooner than that."
    "readme":"compute/resource-manager/readme.md",
    "tag":"package-2022-03-03",
    "details":"Error: 1 errors occured -- cannot continue."
    ⚠️ UnkownSecurityScheme "readme":"compute/resource-manager/readme.md",
    "tag":"package-2022-03-03-only",
    "details":"Security scheme azure_auth is unknown and will not be processed. Only supported types are AADToken,
    AzureKey,
    Anonymous"
    ️️✔️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.
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Aug 18, 2022

    Swagger Generation Artifacts

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

    Breaking Changes Tracking

    azure-sdk-for-go - armcompute - 4.0.0
    +	Function `*CloudServicesClient.BeginCreateOrUpdate` parameter(s) have been changed from `(context.Context, string, string, CloudService, *CloudServicesClientBeginCreateOrUpdateOptions)` to `(context.Context, string, string, *CloudServicesClientBeginCreateOrUpdateOptions)`
    +	Function `*CloudServicesClient.BeginUpdate` parameter(s) have been changed from `(context.Context, string, string, CloudServiceUpdate, *CloudServicesClientBeginUpdateOptions)` to `(context.Context, string, string, *CloudServicesClientBeginUpdateOptions)`
    +	Function `*CloudServicesUpdateDomainClient.BeginWalkUpdateDomain` parameter(s) have been changed from `(context.Context, string, string, int32, UpdateDomain, *CloudServicesUpdateDomainClientBeginWalkUpdateDomainOptions)` to `(context.Context, string, string, int32, *CloudServicesUpdateDomainClientBeginWalkUpdateDomainOptions)`
    azure-sdk-for-python-track2 - track2_azure-mgmt-compute - 27.2.0
    +	Operation VirtualMachineRunCommandsOperations.begin_create_or_update no longer has parameter content_type
    +	Operation VirtualMachineRunCommandsOperations.begin_update no longer has parameter content_type
    +	Operation VirtualMachineScaleSetVMRunCommandsOperations.begin_create_or_update no longer has parameter content_type
    +	Operation VirtualMachineScaleSetVMRunCommandsOperations.begin_update no longer has parameter content_type
    +	Operation VirtualMachineScaleSetVMsOperations.begin_run_command no longer has parameter content_type
    +	Operation VirtualMachinesOperations.begin_run_command no longer has parameter content_type
    ️️✔️ azure-sdk-for-net-track2 succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs] Generate from fa8a024b1c2f3024d771ae8603d3463936597890. 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	File azure-sdk-for-net_tmp/initOutput.json not found to read
      command	pwsh ./eng/scripts/Invoke-GenerateAndBuildV2.ps1 ../azure-sdk-for-net_tmp/generateInput.json ../azure-sdk-for-net_tmp/generateOutput.json
    • ️✔️Azure.ResourceManager.Compute [View full logs]  [Preview SDK Changes]
      info	[Changelog]
    ️⚠️ azure-sdk-for-python-track2 warning [Detail]
    • ⚠️Warning [Logs] Generate from fa8a024b1c2f3024d771ae8603d3463936597890. 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]  global `--global`, `--local` are deprecated. Use `--location=global` instead.
    • ️✔️track2_azure-mgmt-compute [View full logs]  [Preview SDK Changes] Breaking Change Detected
      info	[Changelog] ### Breaking Changes
      info	[Changelog]
      info	[Changelog]   - Operation VirtualMachineRunCommandsOperations.begin_create_or_update no longer has parameter content_type
      info	[Changelog]   - Operation VirtualMachineRunCommandsOperations.begin_update no longer has parameter content_type
      info	[Changelog]   - Operation VirtualMachineScaleSetVMRunCommandsOperations.begin_create_or_update no longer has parameter content_type
      info	[Changelog]   - Operation VirtualMachineScaleSetVMRunCommandsOperations.begin_update no longer has parameter content_type
      info	[Changelog]   - Operation VirtualMachineScaleSetVMsOperations.begin_run_command no longer has parameter content_type
      info	[Changelog]   - Operation VirtualMachinesOperations.begin_run_command no longer has parameter content_type
    ️️✔️ azure-sdk-for-java succeeded [Detail] [Expand]
    ️️✔️ azure-sdk-for-js succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs] Generate from fa8a024b1c2f3024d771ae8603d3463936597890. 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] npm[ERROR] Cannot generate changelog because the codes of local and npm may be the same.
    • ️✔️@azure/arm-compute [View full logs]  [Preview SDK Changes]
      info	[Changelog]
      error	breakingChangeTracking is enabled, but version or changelogItem is not found in output.
    ️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs] Generate from fa8a024b1c2f3024d771ae8603d3463936597890. 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
    • ️✔️armcompute [View full logs]  [Preview SDK Changes] Breaking Change Detected
      info	[Changelog] ### Breaking Changes
      info	[Changelog]
      info	[Changelog] - Function `*CloudServicesClient.BeginCreateOrUpdate` parameter(s) have been changed from `(context.Context, string, string, CloudService, *CloudServicesClientBeginCreateOrUpdateOptions)` to `(context.Context, string, string, *CloudServicesClientBeginCreateOrUpdateOptions)`
      info	[Changelog] - Function `*CloudServicesUpdateDomainClient.BeginWalkUpdateDomain` parameter(s) have been changed from `(context.Context, string, string, int32, UpdateDomain, *CloudServicesUpdateDomainClientBeginWalkUpdateDomainOptions)` to `(context.Context, string, string, int32, *CloudServicesUpdateDomainClientBeginWalkUpdateDomainOptions)`
      info	[Changelog] - Function `*CloudServicesClient.BeginUpdate` parameter(s) have been changed from `(context.Context, string, string, CloudServiceUpdate, *CloudServicesClientBeginUpdateOptions)` to `(context.Context, string, string, *CloudServicesClientBeginUpdateOptions)`
      info	[Changelog] - Type of `SharingProfile.CommunityGalleryInfo` has been changed from `interface{}` to `*CommunityGalleryInfo`
      info	[Changelog]
      info	[Changelog] ### Features Added
      info	[Changelog]
      info	[Changelog] - New field `Parameters` in struct `CloudServicesClientBeginCreateOrUpdateOptions`
      info	[Changelog] - New field `Parameters` in struct `CloudServicesUpdateDomainClientBeginWalkUpdateDomainOptions`
      info	[Changelog] - New field `Parameters` in struct `CloudServicesClientBeginUpdateOptions`
      info	[Changelog]
      info	[Changelog] Total 4 breaking change(s), 3 additive change(s).
    ️⚠️ azure-resource-manager-schemas warning [Detail]
    • ⚠️Warning [Logs] Generate from fa8a024b1c2f3024d771ae8603d3463936597890. 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]  old lockfile
      cmderr	[initScript.sh] npm WARN old lockfile The package-lock.json file was created with an old version of npm,
      cmderr	[initScript.sh] npm WARN old lockfile so supplemental metadata must be fetched from the registry.
      cmderr	[initScript.sh] npm WARN old lockfile
      cmderr	[initScript.sh] npm WARN old lockfile This is a one-time fix-up, please be patient...
      cmderr	[initScript.sh] npm WARN old lockfile
      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
    • ️✔️compute [View full logs]  [Preview Schema Changes]
    ️❌ azure-powershell failed [Detail]
    • Failed [Logs] Generate from fa8a024b1c2f3024d771ae8603d3463936597890. 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.compute [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 Aug 18, 2022

    Generated ApiView

    Language Package Name ApiView Link
    Java azure-resourcemanager-compute-generated https://apiview.dev/Assemblies/Review/6bab8a2dd6694bb6860c0a9ba13fba65
    JavaScript @azure/arm-compute https://apiview.dev/Assemblies/Review/2b67517d873f4f2aa05c18ac5d21e419
    .Net Azure.ResourceManager.Compute There is no API change compared with the previous version
    Python track2_azure-mgmt-compute Create ApiView failed. Please ask PR assignee for help

    @openapi-workflow-bot
    Copy link

    Hi @Sandido, 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.

    Copy link

    Next Steps to Merge

    Next steps that must be taken to merge this PR:
    • ❌ Your PR has breaking changes in the generated SDK for go (label: CI-BreakingChange-Go). Refer to step 3 in the PR workflow diagram (even if your PR is for data plane, not ARM).

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    2 participants