-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
qiaozha
wants to merge
2
commits into
Azure:main
Choose a base branch
from
qiaozha:hybridconnectivity-refactor-clean
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- 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/
Next Steps to MergeNext steps that must be taken to merge this PR:
|
PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
|
- 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
BreakingChange-Go-Sdk-Suppression
BreakingChange-Python-Sdk-Suppression
BreakingChangeReviewRequired
<valid label in PR review process>add this label when breaking change review is required
resource-manager
RPaaS
SuppressionReviewRequired
TypeSpec
Authored with TypeSpec
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.