Release hybridcompute microsoft.hybrid compute 2024 09 10 preview

[vedkale]

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.
• 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:

• I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
• 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 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]

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

[openapi-pipeline-app]

Generated ApiView

Language	Package Name	ApiView Link
Go	sdk/resourcemanager/hybridcompute/armhybridcompute	https://apiview.dev/Assemblies/Review/cc99eb4c91204d199d8e40aed71bc06e?revisionId=29ab9ddc5df14e508a85bbad7cba1d23
JavaScript	@azure/arm-hybridcompute	https://apiview.dev/Assemblies/Review/bd79793b6b53409d8de21847c605dc64?revisionId=7c87fa5b8d0b49bbba81861a3a75d1b4
.Net	Azure.ResourceManager.HybridCompute	There is no API change compared with the previous version
Java	azure-resourcemanager-hybridcompute	https://apiview.dev/Assemblies/Review/b79886348ebe497b9ddc99d286cb6e99?revisionId=2ee983eaedd3482e8633dea4ff915e25
Python	azure-mgmt-hybridcompute	https://apiview.dev/Assemblies/Review/4d8650fb76954c6ba3f15e1781007dd9?revisionId=d9ee4e1cddcc4a5291d7e2cf8d249f30
Swagger	Microsoft.HybridCompute	https://apiview.dev/Assemblies/Review/31dae74112a04fb7b3a4a58e2c398536?revisionId=dbd84c2ef95f4cb78a79e7b6ac0728c7

[jiaqi-beep]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[vedkale]

@TimLovellSmith The API is essentially used for installing a set of VM extensions, currently ARM doesn't support RBAC based on body, and we wanted to expose an API that lets you install certain VM extensions that we think are ok to install. Currently, it the /extensions API lets you install all VM extensions which contain some very powerful extensions that not all customers want to install on their machine. We have no issue with changing the names, we can change this to /addExtensions and change "extensionSetupList" to "extensions". and change 'MachineExtensionSetup' to 'SetupExtensionRequest'.

[raosuhas]

@vedkale Could you also respond to the question about POST not being able be called using the ARM template ? Is it acceptable for your customers to not be able to call setup extentions using an ARM template ? It seems like an big limitation to me.

[vedkale]

@raosuhas that seems ok to me. From what I understand if we were to make this a PUT call, it would require the other actions like DELETE, PATCH and GET. We don't want to add those actions for this API. If my understand is incorrect, we will make it a PUT call.

I also created another PR to change the names like @TimLovellSmith suggested
#31346

[raosuhas]

@raosuhas that seems ok to me. From what I understand if we were to make this a PUT call, it would require the other actions like DELETE, PATCH and GET. We don't want to add those actions for this API. If my understand is incorrect, we will make it a PUT call.

I also created another PR to change the names like @TimLovellSmith suggested #31346

PATCH\DELETE\GET is not a requirement as long as you model it as a Proxy resource. The main problem is that with POST you cannot use this in ARM templates and you cannot use it in ARM Policy

If this is acceptable please have your manager or PM ack this comment.

[raghushantha]

Hi @raosuhas - Thank you for taking the time to review the PR.
We don't intend to use this functionality via Templates or Policy. The API is designed to be used from our Cli experience via the on-premises machine.

ACK'ing your above comment.

[vedkale]

@raosuhas can you also approve this PR to address the naming issues #31346

Issue addressed