Skip to content

refactor: migrate hybridconnectivity to new folder structure #35522

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

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

qiaozha
Copy link
Member

@qiaozha qiaozha commented Jun 27, 2025

  • Moved TypeSpec files from HybridConnectivity.Management/ to resource-manager/Microsoft.HybridConnectivity/HybridConnectivity/
  • Unified TypeSpec and swagger files into single service folder following Azure guidelines
  • Updated common-types references in swagger files for new folder depth
  • Fixed readme.md input-file paths to use relative paths within service folder
  • Updated tspconfig.yaml with correct emitter-output-dir and arm-types-dir
  • Added suppressions.yaml for brownfield services not yet migrated to TypeSpec
  • Preserved all existing tspconfig.yaml options for multiple language SDKs
  • Successfully validated TypeSpec compilation

Follows new folder structure guideline:
specification/{orgName}/resource-manager/{rpNamespace}/{serviceName}/

All files now under: specification/hybridconnectivity/resource-manager/Microsoft.HybridConnectivity/HybridConnectivity/

Choose a PR Template

Switch to "Preview" on this description then select one of the choices below.

Click here to open a PR for a Data Plane API.

Click here to open a PR for a Control Plane (ARM) API.

Click here to open a PR for only SDK configuration.

- Moved TypeSpec files from HybridConnectivity.Management/ to resource-manager/Microsoft.HybridConnectivity/HybridConnectivity/
- Unified TypeSpec and swagger files into single service folder following Azure guidelines
- Updated common-types references in swagger files for new folder depth
- Fixed readme.md input-file paths to use relative paths within service folder
- Updated tspconfig.yaml with correct emitter-output-dir and arm-types-dir
- Added suppressions.yaml for brownfield services not yet migrated to TypeSpec
- Preserved all existing tspconfig.yaml options for multiple language SDKs
- Successfully validated TypeSpec compilation

Follows new folder structure guideline:
specification/{orgName}/resource-manager/{rpNamespace}/{serviceName}/

All files now under: specification/hybridconnectivity/resource-manager/Microsoft.HybridConnectivity/HybridConnectivity/
Copy link

openapi-pipeline-app bot commented Jun 27, 2025

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ This PR targets either the main branch of the public specs repo or the RPSaaSMaster branch of the private specs repo. These branches are not intended for iterative development. Therefore, you must acknowledge you understand that after this PR is merged, the APIs are considered shipped to Azure customers. Any further attempts at in-place modifications to the APIs will be subject to Azure's versioning and breaking change policies. Additionally, for control plane APIs, you must acknowledge that you are following all the best practices documented by ARM at aka.ms/armapibestpractices. If you do intend to release the APIs to your customers by merging this PR, add the PublishToCustomers label to your PR in acknowledgement of the above. Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).
  • ❌ This PR has at least one breaking change (label: BreakingChangeReviewRequired).
    To unblock this PR, follow the process at aka.ms/brch.
  • ❌ The required check named Swagger Avocado 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

Copy link

openapi-pipeline-app bot commented Jun 27, 2025

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

Copy link

github-actions bot commented Jun 27, 2025

API Change Check

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

Language API Review for Package
TypeSpec Microsoft.HybridConnectivity
Go sdk/resourcemanager/hybridconnectivity/armhybridconnectivity
JavaScript @azure/arm-hybridconnectivity
Java com.azure.resourcemanager:azure-resourcemanager-hybridconnectivity
Python azure-mgmt-hybridconnectivity
Swagger Microsoft.HybridConnectivity-HybridConnectivity

- Fix arm-types-dir path to match new folder structure depth
- Update output-file to use dynamic version-status pattern
- Add azure-resource-provider-folder for resource-manager services
- Regenerate swagger with corrected TypeSpec configuration
- Ensure TypeSpec validation passes with proper common-types references
@AzureRestAPISpecReview AzureRestAPISpecReview added BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required resource-manager RPaaS SuppressionReviewRequired TypeSpec Authored with TypeSpec labels Jun 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants