[TSP Migration][HybridConnectivity] TypeSpec migrated from swagger

[pshao25]

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]

PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts.

[openapi-pipeline-app]

PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts.

[openapi-pipeline-app]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ Your PR has breaking changes in the generated SDK for JavaScript (label: BreakingChange-JavaScript-Sdk). Refer to step 3 in the PR workflow diagram.
• ❌ The required check named SDK azure-sdk-for-go has failed. 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 3 in the PR workflow diagram

[openapi-pipeline-app]

Generated ApiView

Language	Package Name	ApiView Link
Java	azure-resourcemanager-hybridconnectivity	https://apiview.dev/Assemblies/Review/29fd73766ecc4053af99904c0d9cb57a?revisionId=46c2ae47adb249bf81b3a2769d21c0ad
Python	azure-mgmt-hybridconnectivity	https://apiview.dev/Assemblies/Review/1eb06095c0924bed813e10739f652bc1?revisionId=70980dc467594e9f8255b36e11f15e3d
JavaScript	@azure/arm-hybridconnectivity	https://apiview.dev/Assemblies/Review/244085e470344d229bc90c8196caf8af?revisionId=f4729571974d42b9b3acd74c7ce06283
TypeSpec	HybridConnectivity.Management	https://apiview.dev/Assemblies/Review/0cbe4b5d6ee04bc286addfa44695ab6b?revisionId=4e86e77900fa406189e76c0e8e6197e8

[azure-sdk]

API change check

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

Microsoft.HybridConnectivity

[pshao25]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[weidongxu-microsoft]

@pshao25

Do you know why the Endponts -> EndpointResources happens in convertion?

It appears Java SDK's break is caused by this pattern (same as the ServiceConfigurations)
#32243 (comment)

[weidongxu-microsoft]

SDK can use @clientName to override this, so not a blocking issue for SDK.
https://github.com/Azure/azure-rest-api-specs/pull/32243/files

[tadelesh]

/azp run

[azure-pipelines]

You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list.