[TSP Migration][domainregistration] TypeSpec migrated from swagger#36733
Merged
pshao25 merged 54 commits intoAzure:mainfrom Jan 12, 2026
Merged
[TSP Migration][domainregistration] TypeSpec migrated from swagger#36733pshao25 merged 54 commits intoAzure:mainfrom
pshao25 merged 54 commits intoAzure:mainfrom
Conversation
v-zhocai
requested review from
mikeharder,
naveedaz and
weshaggard
as code owners
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.Comment generated by summarize-checks workflow run. |
microsoft-github-policy-service
bot
added
the
customer-reported
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
|
v-zhocai
force-pushed
the
convert/domainregistration
branch
from
45d1edc to
2963ef8
Compare
v-zhocai
force-pushed
the
convert/domainregistration
branch
from
2963ef8 to
59119b6
Compare
Member
|
IMPORTANT: Your service is scheduled to be converted to TypeSpec in September Azure SDK engineers will handle the majority of the conversion in a pull request for each service. As the service owner, your role is to collaborate with Azure SDK engineers on the pull request and merge the updates within two weeks. During the conversion, affected services are put on hold to apply updates or introduce new versions. If your service has a scheduling conflict due to high-priority feature delivery or else, reach out to TypeSpec Conversion Board at your earliest convenience. Let’s work together on a solution. |
Added suppress annotations for legacy usage warnings in TypeSpec.
Suppress warnings for secret properties in the model.
pshao25
added
Approved-LintDiff
BreakingChange-Approved-Benign
github-actions
bot
added
WaitForARMFeedback
pshao25
added
PublishToCustomers
github-actions
bot
removed
the
WaitForARMFeedback
pshao25
approved these changes
Jan 12, 2026
Member
|
|
9 tasks
This was referenced Feb 12, 2026
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
6 participants
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.
This PR migrates your latest version (identified by the tag in your readme.md) of swagger to TypeSpec. We already tried our best to make sure the TypeSpec represents same as previous swagger. Since we lack the business knowledge, please validate this PR again to make sure it's functional equivalent as before. The local validation step is at Getting started | TypeSpec Azure
Besides, TypeSpec encourages to follow ARM guidelines. Therefore, some representations in your previous swagger will be fixed to follow these guidelines. When you see differences in your local validation, please keep this note in mind.
Please reach out to TypeSpec Discussions Channel if there is any help needed.