Skip to content

Refactor(edge): migrate to unified folder structure#44445

Draft
v-xuto wants to merge 1 commit into
Azure:mainfrom
v-xuto:edge-refactor
Draft

Refactor(edge): migrate to unified folder structure#44445
v-xuto wants to merge 1 commit into
Azure:mainfrom
v-xuto:edge-refactor

Conversation

@v-xuto

@v-xuto v-xuto commented Jul 6, 2026

Copy link
Copy Markdown
Member

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

Change:

  • Consolidated TypeSpec and Swagger files under
edge
└─ resource-manager
   └─ Microsoft.Edge
      ├─ configurationmanager
      ├─ configurations
      ├─ disconnectedOperations
      ├─ edge
      └─ sites
  • Updated tspconfig.yaml with correct paths and ARM types directory
  • Verified TypeSpec compilation works correctly
  • Updated the relevant paths in specification/suppressions.yaml file
  • Add rpaas readme.md under resource-manger

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 Jul 6, 2026
@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown

Next Steps to Merge

⌛ Please wait. Next steps to merge this PR are being evaluated by automation. ⌛

Comment generated by summarize-checks workflow run.

@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown

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).
  • ❌ 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 RPaaS TypeSpec Authored with TypeSpec labels Jul 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

BreakingChange-JavaScript-Sdk BreakingChange-Python-Sdk FolderMigrationV2 A specific label for PRs like folder structure migration into v2. resource-manager RPaaS TypeSpec Authored with TypeSpec

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant