lijiaq hybridcompute microsoft.hybrid compute 2024 11 10 preview

[jiaqi-beep]

ARM (Control Plane) API Specification Update Pull Request

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

PR review workflow diagram

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

Purpose of this PR

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

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

Due diligence checklist

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

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

Additional information

Viewing API changes

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

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the [suppressions guide](https://aka.ms/azsdk/pr-suppressions) to get approval.

Getting help

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

[openapi-pipeline-app[bot]]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ This PR is in purview of the ARM review (label: ARMReview). This PR must get ARMSignedOff label from an ARM reviewer.
  This PR has ARMChangesRequested label. Please address or respond to feedback from the ARM API reviewer.
  When you are ready to continue the ARM API review, please remove the ARMChangesRequested label.
  Automation should then add WaitForARMFeedback label.
  ❗If you don't have permissions to remove the label, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories.
  For details of the ARM review, see aka.ms/azsdk/pr-arm-review
  
• ❌ The required check named Automated merging requirements met has failed. This is the final check that must pass. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide. In addition, refer to step 4 in the PR workflow diagram

[openapi-pipeline-app[bot]]

Generated ApiView

Language	Package Name	ApiView Link
Go	sdk/resourcemanager/hybridcompute/armhybridcompute	https://apiview.dev/Assemblies/Review/cc99eb4c91204d199d8e40aed71bc06e?revisionId=8271a7b5547945119c794324462ea165
Java	azure-resourcemanager-hybridcompute	https://apiview.dev/Assemblies/Review/b79886348ebe497b9ddc99d286cb6e99?revisionId=7dca2b63ed8a4a86b61d1cef4bacdf23
JavaScript	@azure/arm-hybridcompute	https://apiview.dev/Assemblies/Review/bd79793b6b53409d8de21847c605dc64?revisionId=42d81c29f2d34b42ab0beede7cd0fcfe
.Net	Azure.ResourceManager.HybridCompute	There is no API change compared with the previous version
Python	azure-mgmt-hybridcompute	https://apiview.dev/Assemblies/Review/4d8650fb76954c6ba3f15e1781007dd9?revisionId=bb9d4a3b352a41b8b7b402632b025f0b

[jiaqi-beep]

This preview has been signed off, but we want to include the change in a separate preview instead https://github.com/Azure/azure-rest-api-specs/pull/30656

[azure-sdk]

API change check

APIView has identified API level changes in this PR and created following API reviews.

preview

[jiaqi-beep]

@tadelesh , @qiaozha , @weidongxu-microsoft , @msyyc , can you help check why azure-sdk-for-* checks all failed?

[jiaqi-beep]

breaking change previously approved in #29560

[ms-bogdan-rotaru]

I'm comparing HybridCompute.json specification from this PR with the base spec at this path: https://github.com/Azure/azure-rest-api-specs/blob/8e0591326d2eb5e0dcb8b284377de87eb1f105f4/specification/hybridcompute/resource-manager/Microsoft.HybridCompute/preview/2024-07-31-preview/HybridCompute.json

There are some differences on using the common types, can you please check?

[ms-bogdan-rotaru]

Additionally - you pushed some more changes in the last commit after the PR has been signed off.

[jiaqi-beep]

Additionally - you pushed some more changes in the last commit after the PR has been signed off.

yep. It was signed off before it was ready

[jiaqi-beep]

@ms-bogdan-rotaru We made the change to use v3 common types in these PR, please check. This was to fix some breaking change check fails. https://github.com/Azure/azure-rest-api-specs/pull/30546 <-- https://github.com/Azure/azure-rest-api-specs/pull/31063