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

Removed all examples and specifications for api version 2021-04-04-pr… #22413

Merged
merged 3 commits into from
Mar 27, 2023

Conversation

dk1729
Copy link
Contributor

@dk1729 dk1729 commented Feb 1, 2023

ARM API Information (Control Plane)

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
    • Removing a preview version.
  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. By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

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 apply 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 copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For 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 you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.

NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)

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

@openapi-workflow-bot
Copy link

Hi, @dk1729 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 Feb 1, 2023

    Swagger Validation Report

    ️❌BreakingChange: 35 Errors, 0 Warnings failed [Detail]
    compared swaggers (via Oad v0.10.4)] new version base version
    orbital.json 2021-04-04-preview(529300e) 2021-04-04-preview(main)

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

    Rule Message
    1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/providers/Microsoft.Orbital/operations' removed or restructured?
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L33:5
    1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/providers/Microsoft.Orbital/spacecrafts' removed or restructured?
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L69:5
    1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Orbital/spacecrafts' removed or restructured?
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L108:5
    1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Orbital/spacecrafts/{spacecraftName}' removed or restructured?
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L150:5
    1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Orbital/spacecrafts/{spacecraftName}/contacts' removed or restructured?
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L348:5
    1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Orbital/spacecrafts/{spacecraftName}/contacts/{contactName}' removed or restructured?
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L393:5
    1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Orbital/spacecrafts/{spacecraftName}/listAvailableContacts' removed or restructured?
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L550:5
    1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Orbital/contactProfiles/{contactProfileName}' removed or restructured?
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L606:5
    1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/providers/Microsoft.Orbital/contactProfiles' removed or restructured?
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L804:5
    1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Orbital/contactProfiles' removed or restructured?
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L843:5
    1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/providers/Microsoft.Orbital/availableGroundStations' removed or restructured?
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L885:5
    1005 - RemovedPath The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/providers/Microsoft.Orbital/availableGroundStations/{groundStationName}' removed or restructured?
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L927:5
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'TagsObject' removed or renamed?
    New: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L33:3
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L967:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'SpacecraftsProperties' removed or renamed?
    New: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L33:3
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L967:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'Spacecraft' removed or renamed?
    New: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L33:3
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L967:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'ResourceReference' removed or renamed?
    New: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L33:3
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L967:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'ContactsProperties' removed or renamed?
    New: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L33:3
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L967:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'ContactProfilesProperties' removed or renamed?
    New: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L33:3
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L967:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'ContactProfile' removed or renamed?
    New: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L33:3
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L967:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'ContactParameters' removed or renamed?
    New: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L33:3
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L967:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'Contact' removed or renamed?
    New: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L33:3
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L967:3
    1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'systemData' removed or renamed?
    New: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L33:3
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L967:3
    1007 - RemovedClientParameter The new version is missing a client parameter that was found in the old version. Was 'contactNameParameter' removed or renamed?
    New: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L34:3
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L1757:3
    1007 - RemovedClientParameter The new version is missing a client parameter that was found in the old version. Was 'contactProfileNameParameter' removed or renamed?
    New: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L34:3
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L1757:3
    1007 - RemovedClientParameter The new version is missing a client parameter that was found in the old version. Was 'groundStationNameParameter' removed or renamed?
    New: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L34:3
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L1757:3
    1007 - RemovedClientParameter The new version is missing a client parameter that was found in the old version. Was 'spacecraftNameParameter' removed or renamed?
    New: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L34:3
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L1757:3
    1007 - RemovedClientParameter The new version is missing a client parameter that was found in the old version. Was 'capabilityParameter' removed or renamed?
    New: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L34:3
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L1757:3
    1007 - RemovedClientParameter The new version is missing a client parameter that was found in the old version. Was 'orbitalGatewayNameParameter' removed or renamed?
    New: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L34:3
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L1757:3
    1007 - RemovedClientParameter The new version is missing a client parameter that was found in the old version. Was 'edgeSiteNameParameter' removed or renamed?
    New: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L34:3
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L1757:3
    1007 - RemovedClientParameter The new version is missing a client parameter that was found in the old version. Was 'l2ConnectionNameParameter' removed or renamed?
    New: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L34:3
    Old: Microsoft.Orbital/preview/2021-04-04-preview/orbital.json#L1757:3
    ️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
    There are no breaking changes.
    ️️✔️CredScan succeeded [Detail] [Expand]
    There is no credential detected.
    ️️✔️LintDiff succeeded [Detail] [Expand]
    Validation passes for LintDiff.
    compared tags (via openapi-validator v2.0.0) new version base version
    default default(529300e) default(main)
    ️️✔️Avocado succeeded [Detail] [Expand]
    Validation passes for Avocado.
    ️️✔️ApiReadinessCheck succeeded [Detail] [Expand]
    ️️✔️~[Staging] ServiceAPIReadinessTest succeeded [Detail] [Expand]
    Validation passes for ServiceAPIReadinessTest.
    ️❌SwaggerAPIView: 0 Errors, 1 Warnings failed [Detail]
    Rule Message
    ⚠️ Failed to generate swagger APIView. The readme file format is invalid and the tag is not defined. Use the provided readme template for guidance readme template. For more details, please check the detail log. "How to fix":"Check the readme file and make sure the readme file format is valid and the tag is defined. Use the provided readme template"
    ️️✔️CadlAPIView 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.
    ️️✔️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?

    @ghost ghost added the customer-reported Issues that are reported by GitHub users external to the Azure organization. label Feb 1, 2023
    @ghost
    Copy link

    ghost commented Feb 1, 2023

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

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Feb 1, 2023

    Swagger Generation Artifacts

    ️️✔️ApiDocPreview succeeded [Detail] [Expand]
    ️❌SDK Breaking Change Tracking failed [Detail]

    Breaking Changes Tracking

    azure-sdk-for-go - sdk/resourcemanager/orbital/armorbital - 2.0.0
    -	Field `Etag` of struct `ContactProfile` has been removed
    -	Field `Etag` of struct `Contact` has been removed
    -	Field `Etag` of struct `Spacecraft` has been removed
    -	Function `*AvailableGroundStationsClient.Get` has been removed
    -	Type alias `APIVersionParameter` has been removed
    azure-sdk-for-python-track2 - track2_azure-mgmt-orbital - 1.1.0b1
    -	Model Contact no longer has parameter etag
    -	Model ContactProfile no longer has parameter etag
    -	Model Spacecraft no longer has parameter etag
    -	Parameter contact_profile of model Contact is now required
    -	Parameter expiration_date of model AuthorizedGroundstation is now required
    -	Parameter ground_station of model AuthorizedGroundstation is now required
    -	Parameter ground_station_name of model Contact is now required
    -	Parameter id of model AvailableContactsSpacecraft is now required
    -	Parameter id of model ContactParametersContactProfile is now required
    -	Parameter id of model ContactsPropertiesContactProfile is now required
    -	Parameter id of model ResourceReference is now required
    -	Parameter links of model ContactProfile is now required
    -	Parameter links of model Spacecraft is now required
    -	Parameter network_configuration of model ContactProfile is now required
    -	Parameter reservation_end_time of model Contact is now required
    -	Parameter reservation_start_time of model Contact is now required
    -	Parameter title_line of model Spacecraft is now required
    -	Parameter tle_line1 of model Spacecraft is now required
    -	Parameter tle_line2 of model Spacecraft is now required
    -	Removed operation AvailableGroundStationsOperations.get
    azure-sdk-for-js - @azure/arm-orbital - 2.0.0
    -	Interface Contact no longer has parameter etag
    -	Interface ContactProfile no longer has parameter etag
    -	Interface ContactProfilesCreateOrUpdateOptionalParams no longer has parameter links
    -	Interface ContactProfilesCreateOrUpdateOptionalParams no longer has parameter networkConfiguration
    -	Interface Spacecraft no longer has parameter etag
    -	Interface SpacecraftsCreateOrUpdateOptionalParams no longer has parameter links
    -	Interface SpacecraftsCreateOrUpdateOptionalParams no longer has parameter titleLine
    -	Interface SpacecraftsCreateOrUpdateOptionalParams no longer has parameter tleLine1
    -	Interface SpacecraftsCreateOrUpdateOptionalParams no longer has parameter tleLine2
    -	Operation ContactProfiles.beginCreateOrUpdate has a new signature
    -	Operation ContactProfiles.beginCreateOrUpdateAndWait has a new signature
    -	Operation Spacecrafts.beginCreateOrUpdate has a new signature
    -	Operation Spacecrafts.beginCreateOrUpdateAndWait has a new signature
    -	Parameter contactProfile of interface Contact is now required
    -	Parameter expirationDate of interface AuthorizedGroundstation is now required
    -	Parameter groundStation of interface AuthorizedGroundstation is now required
    -	Parameter groundStationName of interface Contact is now required
    -	Parameter id of interface ResourceReference is now required
    -	Parameter links of interface ContactProfile is now required
    -	Parameter links of interface Spacecraft is now required
    -	Parameter networkConfiguration of interface ContactProfile is now required
    -	Parameter reservationEndTime of interface Contact is now required
    -	Parameter reservationStartTime of interface Contact is now required
    -	Parameter titleLine of interface Spacecraft is now required
    -	Parameter tleLine1 of interface Spacecraft is now required
    -	Parameter tleLine2 of interface Spacecraft is now required
    -	Removed Enum KnownApiVersionParameter
    -	Removed operation AvailableGroundStations.get
    +	Interface ContactProfilesListBySubscriptionNextOptionalParams no longer has parameter skiptoken
    +	Interface ContactProfilesListNextOptionalParams no longer has parameter skiptoken
    +	Interface ContactsListNextOptionalParams no longer has parameter skiptoken
    +	Interface SpacecraftsListBySubscriptionNextOptionalParams no longer has parameter skiptoken
    +	Interface SpacecraftsListNextOptionalParams no longer has parameter skiptoken
    ️⚠️ azure-sdk-for-python-track2 warning [Detail]
    • ⚠️Warning [Logs]Release - Generate from dfa60ad. 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] npm notice
      cmderr	[automation_generate.sh] npm notice New minor version of npm available! 9.5.0 -> 9.6.2
      cmderr	[automation_generate.sh] npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.6.2>
      cmderr	[automation_generate.sh] npm notice Run `npm install -g npm@9.6.2` to update!
      cmderr	[automation_generate.sh] npm notice
    • ️✔️track2_azure-mgmt-orbital [View full logs]  [Release SDK Changes]
      info	[Changelog]
    ️️✔️ azure-sdk-for-java succeeded [Detail] [Expand]
    ️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs]Release - Generate from dfa60ad. 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/orbital/armorbital [View full logs]  [Release SDK Changes]
      info	[Changelog] ### Other Changes
      info	[Changelog]
      info	[Changelog] Total 0 breaking change(s), 0 additive change(s).
    ️️✔️ azure-sdk-for-js succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs]Release - Generate from dfa60ad. 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] Cannot generate changelog because the codes of local and npm may be the same.
    • ️✔️@azure/arm-orbital [View full logs]  [Release SDK Changes]
      info	[Changelog]
      error	breakingChangeTracking is enabled, but version or changelogItem is not found in output.
    ️⚠️ azure-resource-manager-schemas warning [Detail]
    • ⚠️Warning [Logs]Release - Generate from dfa60ad. 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]
      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
    • ️✔️orbital [View full logs]  [Release Schema Changes]
    ️️✔️ azure-powershell succeeded [Detail] [Expand]
    • ️✔️Succeeded [Logs]Release - Generate from dfa60ad. 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.orbital.DefaultTag [View full logs]  [Release SDK Changes]
    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-pipeline-app
    Copy link

    openapi-pipeline-app bot commented Feb 1, 2023

    Generated ApiView

    Language Package Name ApiView Link
    Go sdk/resourcemanager/orbital/armorbital https://apiview.dev/Assemblies/Review/c8c340605b0642779a66364d38878595
    Java azure-resourcemanager-orbital https://apiview.dev/Assemblies/Review/8a5de8bb96364c5ca6fbd36afe77cdbf
    JavaScript @azure/arm-orbital https://apiview.dev/Assemblies/Review/b90b946419eb4477b0739601045813ca

    @openapi-workflow-bot
    Copy link

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

    @openapi-workflow-bot
    Copy link

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

    @honghr honghr assigned raych1 and unassigned honghr Mar 22, 2023
    @raych1
    Copy link
    Member

    raych1 commented Mar 24, 2023

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

    @dk1729 , can you follow above action to get approval because of removing an api version?

    @raych1 raych1 added Reviewed-ChangesRequested <valid label in PR review process>add this label when assignee request changes after review Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 labels Mar 24, 2023
    @raych1 raych1 removed the Reviewed-ChangesRequested <valid label in PR review process>add this label when assignee request changes after review label Mar 27, 2023
    @raych1
    Copy link
    Member

    raych1 commented Mar 27, 2023

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

    @dk1729 , can you follow above action to get approval because of removing an api version?

    Synced offline, this is a preview version and doesn't need approval.

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    Approved-BreakingChange DO NOT USE! OBSOLETE label. See https://github.com/Azure/azure-sdk-tools/issues/6374 BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required CI-BreakingChange-Go CI-BreakingChange-JavaScript customer-reported Issues that are reported by GitHub users external to the Azure organization. resource-manager
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    4 participants