Skip to content

Conversation

@v-xuto
Copy link
Member

@v-xuto v-xuto commented Nov 17, 2025

This PR migrates the migrate specification to the new unified folder structure according to Azure folder structure guidelines.

Change:

  • Consolidated TypeSpec and Swagger files under
resource-manager
├── Microsoft.Migrate/
│   ├── AKSAssessments
│   ├── AssessmentProjects
│   ├── AvsAssessments         
│   ├── BusinessCases
│   ├── Collectors
│   ├── HeterogenousAssessments
│   ├── MachineAssessments
│   ├── MigrateProjects
│   ├── MordernizeProjects
│   ├── SqlAssessments
│   ├── Waves
│   ├── WebAppAssessments
│   └── WebAppCompoundAssessments
└── Microsoft.OffAzure/OffAzure
  • Updated tspconfig.yaml with correct paths and ARM types directory
  • Fixed all common-types references and input-file paths in readme.md
  • Added suppressions.yaml for legacy API versions
  • Verified TypeSpec compilation works correctly
  • Updated the relevant paths in specification/suppressions.yaml file
  • Updated the relevant paths in cspell.yaml file

Benefits:

  • Unified structure for better maintainability
  • Aligns with Azure folder structure standards
  • Maintains backward compatibility
  • Supports future TypeSpec migration efforts

@v-xuto v-xuto added the FolderMigrationV2 A specific label for PRs like folder structure migration into v2. label Nov 17, 2025
@github-actions
Copy link

github-actions bot commented Nov 17, 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 TypeSpec Validation 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


Comment generated by summarize-checks workflow run.

@github-actions github-actions bot added resource-manager BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required labels Nov 17, 2025
@github-actions
Copy link

github-actions bot commented Nov 17, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required FolderMigrationV2 A specific label for PRs like folder structure migration into v2. resource-manager

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant