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 idleShutdownSetting to Compute Instances #19748

Conversation

teochaban
Copy link
Contributor

@teochaban teochaban commented Jul 12, 2022

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

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.

@openapi-workflow-bot
Copy link

Hi, @teochaban 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 Jul 12, 2022

    Swagger Validation Report

    ️️✔️BreakingChange succeeded [Detail] [Expand]
    There are no breaking changes.
    ️⚠️Breaking Change(Cross-Version): 22 Warnings warning [Detail]
    compared swaggers (via Oad v0.9.6)] new version base version
    machineLearningServices.json 2022-06-01(224c53e) 2022-05-01(main)
    machineLearningServices.json 2022-06-01(224c53e) 2022-02-01(main)

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

    Rule Message
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'WorkspaceConnection' removed or renamed?
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L2025:3
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/machineLearningServices.json#L1978:3
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'WorkspaceConnectionProps' removed or renamed?
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L2025:3
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/machineLearningServices.json#L1978:3
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'ScheduleType' removed or renamed?
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L2025:3
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/machineLearningServices.json#L1978:3
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'RecurrencePattern' removed or renamed?
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L2025:3
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/machineLearningServices.json#L1978:3
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'RecurrenceFrequency' removed or renamed?
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L2025:3
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/machineLearningServices.json#L1978:3
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'RecurrenceSchedule' removed or renamed?
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L2025:3
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/machineLearningServices.json#L1978:3
    ⚠️ 1006 - RemovedDefinition The new version is missing a definition that was found in the old version. Was 'CronSchedule' removed or renamed?
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L2025:3
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/machineLearningServices.json#L1978:3
    ⚠️ 1022 - RemovedAdditionalProperties The new version removes the 'additionalProperties' element.
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L3579:9
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/machineLearningServices.json#L3505:9
    ⚠️ 1029 - ReadonlyPropertyChanged The read only property has changed from 'false' to 'true'.
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L5536:9
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/machineLearningServices.json#L5175:9
    ⚠️ 1030 - DifferentDiscriminator The new version has a different discriminator than the previous one.
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L5521:9
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/machineLearningServices.json#L5191:9
    ⚠️ 1030 - DifferentDiscriminator The new version has a different discriminator than the previous one.
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L4917:9
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/machineLearningServices.json#L4809:9
    ⚠️ 1030 - DifferentDiscriminator The new version has a different discriminator than the previous one.
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L4922:5
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/mfe.json#L12325:5
    ⚠️ 1033 - RemovedProperty The new version is missing a property found in the old version. Was 'endTime' renamed or removed?
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L4924:7
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/mfe.json#L12331:7
    ⚠️ 1033 - RemovedProperty The new version is missing a property found in the old version. Was 'scheduleStatus' renamed or removed?
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L4924:7
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/mfe.json#L12331:7
    ⚠️ 1033 - RemovedProperty The new version is missing a property found in the old version. Was 'scheduleType' renamed or removed?
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L4924:7
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/mfe.json#L12331:7
    ⚠️ 1033 - RemovedProperty The new version is missing a property found in the old version. Was 'startTime' renamed or removed?
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L4924:7
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/mfe.json#L12331:7
    ⚠️ 1033 - RemovedProperty The new version is missing a property found in the old version. Was 'timeZone' renamed or removed?
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L4924:7
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/mfe.json#L12331:7
    ⚠️ 1034 - AddedRequiredProperty The new version has new required property 'authType' that was not found in the old version.
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L5521:9
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/machineLearningServices.json#L5191:9
    ⚠️ 1034 - AddedRequiredProperty The new version has new required property 'properties' that was not found in the old version.
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L5532:11
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/machineLearningServices.json#L5171:11
    ⚠️ 1034 - AddedRequiredProperty The new version has new required property 'properties' that was not found in the old version.
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L1711:13
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/machineLearningServices.json#L1717:13
    ⚠️ 1034 - AddedRequiredProperty The new version has new required property 'properties' that was not found in the old version.
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L1719:13
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/machineLearningServices.json#L1725:13
    ⚠️ 1034 - AddedRequiredProperty The new version has new required property 'properties' that was not found in the old version.
    New: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L1761:13
    Old: Microsoft.MachineLearningServices/preview/2022-02-01-preview/machineLearningServices.json#L1768:13
    ️⚠️LintDiff: 1 Warnings warning [Detail]
    compared tags (via openapi-validator v1.13.0) new version base version
    package-preview-2022-06 package-preview-2022-06(224c53e) package-preview-2022-06(dev-machinelearningservices-Microsoft.MachineLearningServices-2022-06-01-preview)

    The following errors/warnings are introduced by current PR:

    Rule Message
    ⚠️ R2063 - OperationIdNounConflictingModelNames OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'ComputeModel'. Consider using the plural form of 'Compute' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L1278


    The following errors/warnings exist before current PR submission:

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

    Rule Message
    R3008 - CollectionObjectPropertiesNaming Collection object 'AmlComputeNodesInformation' returned by list operation 'Compute_ListNodes' with 'x-ms-pageable' extension, has no property named 'value'.
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L1031
    ⚠️ R1003 - ListInOperationName Since operation 'QuotasUpdate' response has model definition 'array', it should be of the form 'list'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L567
    ⚠️ R2001 - AvoidNestedProperties Consider using x-ms-client-flatten to provide a better end user experience
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L3193
    ⚠️ R2001 - AvoidNestedProperties Consider using x-ms-client-flatten to provide a better end user experience
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L3294
    ⚠️ R2001 - AvoidNestedProperties Consider using x-ms-client-flatten to provide a better end user experience
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L3389
    ⚠️ R2001 - AvoidNestedProperties Consider using x-ms-client-flatten to provide a better end user experience
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L3602
    ⚠️ R2001 - AvoidNestedProperties Consider using x-ms-client-flatten to provide a better end user experience
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L3780
    ⚠️ R2001 - AvoidNestedProperties Consider using x-ms-client-flatten to provide a better end user experience
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L3801
    ⚠️ R2001 - AvoidNestedProperties Consider using x-ms-client-flatten to provide a better end user experience
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L3869
    ⚠️ R2001 - AvoidNestedProperties Consider using x-ms-client-flatten to provide a better end user experience
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L3912
    ⚠️ R2001 - AvoidNestedProperties Consider using x-ms-client-flatten to provide a better end user experience
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L3932
    ⚠️ R2001 - AvoidNestedProperties Consider using x-ms-client-flatten to provide a better end user experience
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L3947
    ⚠️ R2001 - AvoidNestedProperties Consider using x-ms-client-flatten to provide a better end user experience
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L4217
    ⚠️ R2001 - AvoidNestedProperties Consider using x-ms-client-flatten to provide a better end user experience
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L5521
    ⚠️ R2001 - AvoidNestedProperties Consider using x-ms-client-flatten to provide a better end user experience
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L5701
    ⚠️ R2029 - PageableOperation Based on the response model schema, operation 'VirtualMachineSizes_List' might be pageable. Consider adding the x-ms-pageable extension.
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L519
    ⚠️ R2029 - PageableOperation Based on the response model schema, operation 'PrivateLinkResources_List' might be pageable. Consider adding the x-ms-pageable extension.
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L1510
    ⚠️ R2029 - PageableOperation Based on the response model schema, operation 'Workspaces_ListOutboundNetworkDependenciesEndpoints' might be pageable. Consider adding the x-ms-pageable extension.
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L1872
    ⚠️ R2063 - OperationIdNounConflictingModelNames OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'ComputeModel'. Consider using the plural form of 'Compute' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L713
    ⚠️ R2063 - OperationIdNounConflictingModelNames OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'ComputeModel'. Consider using the plural form of 'Compute' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L759
    ⚠️ R2063 - OperationIdNounConflictingModelNames OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'ComputeModel'. Consider using the plural form of 'Compute' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L812
    ⚠️ R2063 - OperationIdNounConflictingModelNames OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'ComputeModel'. Consider using the plural form of 'Compute' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L893
    ⚠️ R2063 - OperationIdNounConflictingModelNames OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'ComputeModel'. Consider using the plural form of 'Compute' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L947
    ⚠️ R2063 - OperationIdNounConflictingModelNames OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'ComputeModel'. Consider using the plural form of 'Compute' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L1009
    ⚠️ R2063 - OperationIdNounConflictingModelNames OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'ComputeModel'. Consider using the plural form of 'Compute' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L1101
    ⚠️ R2063 - OperationIdNounConflictingModelNames OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'ComputeModel'. Consider using the plural form of 'Compute' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L1147
    ⚠️ R2063 - OperationIdNounConflictingModelNames OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'ComputeModel'. Consider using the plural form of 'Compute' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L1191
    ⚠️ R2063 - OperationIdNounConflictingModelNames OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'ComputeModel'. Consider using the plural form of 'Compute' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change.
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L1235
    ⚠️ R2066 - PostOperationIdContainsUrlVerb OperationId should contain the verb: 'updatequotas' in:'Quotas_Update'. Consider updating the operationId
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L567
    ⚠️ R3010 - TrackedResourceListByImmediateParent The child tracked resource, 'computes' with immediate parent 'Workspace', must have a list by immediate parent operation.
    Location: Microsoft.MachineLearningServices/preview/2022-06-01-preview/machineLearningServices.json#L3155
    ️️✔️Avocado succeeded [Detail] [Expand]
    Validation passes for Avocado.
    ️️✔️ModelValidation succeeded [Detail] [Expand]
    Validation passes for ModelValidation.
    ️️✔️SemanticValidation succeeded [Detail] [Expand]
    Validation passes for SemanticValidation.
    ️⚠️SDK Track2 Validation: 0 Warnings warning [Detail]
    • The following tags are being changed in this PR
      • "https://github.com/Azure/azure-rest-api-specs/blob/224c53e9da685165c6946f3f575175829c21b617/specification/machinelearningservices/resource-manager/readme.md#tag-package-preview-2022-06">machinelearningservices/resource-manager/readme.md#package-preview-2022-06
    The following errors/warnings exist before current PR submission:
    Rule Message
    ⚠️ UnkownSecurityScheme "readme":"machinelearningservices/resource-manager/readme.md",
    "tag":"package-preview-2022-06",
    "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.
    ️️✔️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 Jul 12, 2022

    Swagger Generation Artifacts

    ️️✔️ApiDocPreview succeeded [Detail] [Expand]

    Only 0 items are rendered, please refer to log for more details.

    ️⚠️SDK Breaking Change Tracking warning [Detail]

    Only 0 items are rendered, please refer to log for more details.

    ️️✔️ azure-sdk-for-net-track2 succeeded [Detail] [Expand]

    Only 0 items are rendered, please refer to log for more details.

    ️️✔️ azure-sdk-for-go succeeded [Detail] [Expand]

    Only 0 items are rendered, please refer to log for more details.

    ️⚠️ azure-sdk-for-python-track2 warning [Detail]

    Only 0 items are rendered, please refer to log for more details.

    ️️✔️ azure-sdk-for-java succeeded [Detail] [Expand]

    Only 0 items are rendered, please refer to log for more details.

    ️⚠️ azure-sdk-for-js warning [Detail]

    Only 0 items are rendered, please refer to log for more details.

    ️⚠️ azure-resource-manager-schemas warning [Detail]

    Only 0 items are rendered, please refer to log for more details.

    ️❌ azure-powershell failed [Detail]

    Only 0 items are rendered, please refer to log for more details.

    Posted by Swagger Pipeline | How to fix these errors?

    @openapi-workflow-bot openapi-workflow-bot bot added ARMReview WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Jul 13, 2022
    @openapi-workflow-bot
    Copy link

    Hi, @teochaban your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board([email protected]).

    @mentat9
    Copy link
    Member

    mentat9 commented Jul 14, 2022

    @teochaban - Please study the guidelines described in the submission form and attest to that by checking the box:

    [ ] 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.

    @mentat9 mentat9 added the ARMChangesRequested <valid label in PR review process>add this label when require changes after ARM review label Jul 14, 2022
    @openapi-workflow-bot
    Copy link

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

    @openapi-workflow-bot openapi-workflow-bot bot removed the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Jul 14, 2022
    @mentat9 mentat9 removed the ARMChangesRequested <valid label in PR review process>add this label when require changes after ARM review label Jul 14, 2022
    @openapi-workflow-bot openapi-workflow-bot bot added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Jul 14, 2022
    @mentat9 mentat9 added ARMChangesRequested <valid label in PR review process>add this label when require changes after ARM review and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Jul 14, 2022
    @openapi-workflow-bot
    Copy link

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

    @teochaban teochaban removed the ARMChangesRequested <valid label in PR review process>add this label when require changes after ARM review label Jul 15, 2022
    @openapi-workflow-bot openapi-workflow-bot bot added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Jul 15, 2022
    @mentat9 mentat9 added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed BreakingChangeReviewRequired labels Jul 15, 2022
    @openapi-workflow-bot openapi-workflow-bot bot removed the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Jul 15, 2022
    @teochaban teochaban added WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required and removed ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review labels Jul 15, 2022
    @mentat9 mentat9 added the ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review label Jul 15, 2022
    @openapi-workflow-bot openapi-workflow-bot bot removed the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Jul 15, 2022
    @teochaban teochaban merged commit b11e89f into Azure:dev-machinelearningservices-Microsoft.MachineLearningServices-2022-06-01-preview Jul 16, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    ARMReview ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review CI-BreakingChange-Go
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    7 participants