[RecoveryServicesBackupCrr] New TypeSpec project for CRR, stable 2026-07-15#44457
Draft
bharatpurwar wants to merge 2 commits into
Draft
[RecoveryServicesBackupCrr] New TypeSpec project for CRR, stable 2026-07-15#44457bharatpurwar wants to merge 2 commits into
bharatpurwar wants to merge 2 commits into
Conversation
…01-15 Swagger (raw converter output) Create a new TOP-LEVEL service folder specification/recoveryservicesbackupcrr/ for the passive-stamp Cross-Region-Restore (CRR) surface, and bootstrap a dedicated TypeSpec project by converting the legacy hand-authored stable/2023-01-15/bms.json. - New folder: recoveryservicesbackupcrr/resource-manager/Microsoft.RecoveryServices/RecoveryServicesBackupCrr/ - Generated via: npx tsp-client convert --arm --fully-compatible (from 2023-01-15 CRR bms.json) - Files (raw converter output, NOT yet customized): main.tsp, models.tsp (119 models / 27 unions / 3 enums), routes.tsp (8 CRR operation groups), RecoveryPointResource.tsp, BackupResourceConfigResource.tsp, back-compatible.tsp, tspconfig.yaml, and examples/2023-01-15/ (18 example JSONs). This is a bootstrap-only checkpoint. Still TODO (next commits): retarget to stable version 2026-07-15, CRR-specific SDK package names, route/casing/pageable/odata/response-code fidelity fixes, common-types v6, lint config, and the WorkloadCrrAccessToken MSI model change. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Step 3 of the CRR (cross-region-restore) TypeSpec migration into the new top-level specification/recoveryservicesbackupcrr/ project. Source changes only; the generated stable/2026-07-15/ swagger output (bms.json + emitted example copies) is intentionally NOT committed yet. main.tsp: - Versions enum -> single stable v2026_07_15: "2026-07-15" - real @doc service description - @service title "Recovery Services Backup CRR Client" - @armCommonTypesVersion CommonTypes.Versions.v6 tspconfig.yaml: - replaced with mirrored ARM emitter config - distinct ...crr SDK package names (Azure.ResourceManager.RecoveryServicesBackupCrr, azure-mgmt-recoveryservicesbackupcrr, azure-resourcemanager-recoveryservicesbackupcrr, @azure/arm-recoveryservicesbackupcrr, armrecoveryservicesbackupcrr) examples: - moved examples/2023-01-15 -> examples/2026-07-15 and retagged api-version Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Next Steps to MergeNext steps that must be taken to merge this PR:
Comment generated by summarize-checks workflow run. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
Comment generated by After APIView workflow run. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Migrates the Azure Backup Cross-Region-Restore (CRR / passive-stamp) API surface from the legacy hand-authored Swagger (
stable/2023-01-15/bms.json) into a new dedicated top-level TypeSpec project atspecification/recoveryservicesbackupcrr/, publishing a new stable API version 2026-07-15.Commits
tsp-client convert(raw converter output).2026-07-15, service title, description, common-types v6), tspconfig.yaml (ARM emitters + distinct...crrSDK package names), examples moved2023-01-15->2026-07-15and retagged.Not yet included (tracked, coming next)
stable/2026-07-15/bms.jsonoutput (intentionally held back)Resource-base migration, x-ms-pageable / x-ms-odata, getAccessToken 400, raw-@routeCRR ops, Tracked->Proxy, enum-doc cleanupWorkloadCrrAccessTokenNotes
Microsoft.RecoveryServices(unchanged); this is a repo/CODEOWNERS reorganization into a dedicated top-level folder.missing-operations-endpointwill be suppressed.