[Typespec Migration] migrate control plane containerregistry to typespec#37169
[Typespec Migration] migrate control plane containerregistry to typespec#37169pshao25 merged 48 commits intoAzure:mainfrom
Conversation
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. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews |
...nager/Microsoft.ContainerRegistry/Registry/preview/2025-05-01-preview/containerregistry.json
Outdated
Show resolved
Hide resolved
...nager/Microsoft.ContainerRegistry/Registry/preview/2025-05-01-preview/containerregistry.json
Outdated
Show resolved
Hide resolved
...nager/Microsoft.ContainerRegistry/Registry/preview/2025-05-01-preview/containerregistry.json
Show resolved
Hide resolved
...nager/Microsoft.ContainerRegistry/Registry/preview/2025-05-01-preview/containerregistry.json
Outdated
Show resolved
Hide resolved
...nager/Microsoft.ContainerRegistry/Registry/preview/2025-05-01-preview/containerregistry.json
Show resolved
Hide resolved
...nager/Microsoft.ContainerRegistry/Registry/preview/2025-05-01-preview/containerregistry.json
Outdated
Show resolved
Hide resolved
...tion/containerregistry/resource-manager/Microsoft.ContainerRegistry/RegistryTasks/models.tsp
Outdated
Show resolved
Hide resolved
...ication/containerregistry/resource-manager/Microsoft.ContainerRegistry/Registry/Registry.tsp
Show resolved
Hide resolved
| namespace Microsoft.ContainerRegistry; | ||
|
|
||
| model MyPrivateLinkResource is PrivateLink; | ||
| alias PrivateLinkOperations = PrivateLinks<MyPrivateLinkResource>; |
There was a problem hiding this comment.
I referred to the test case in this PR to modify the typespec code to support arm PrivateLinkResource template for this service
There was a problem hiding this comment.
But the MyPRivateLinkResource is not the defined name in swagger.
There was a problem hiding this comment.
this would not affect swagger and sdk generation.
Do you think it is better to use
alias PrivateLinkOperations = PrivateLinks<PrivateLink>;
directly to reduce confusion?
There was a problem hiding this comment.
It affected Go SDK generation. We generated the resource with MyPRivateLinkResource name. Could you reach out to @pshao25 to see how to express it.
There was a problem hiding this comment.
I have updated the code in ee1656a#diff-5a63799561fd0b3b14e61e5e0f6de5cf19217505b23b1bf769babae5a60de2f4
could you help check again?
There was a problem hiding this comment.
We have tested the converted version. The resource model name has been changed from PrivateLinkResource to PrivateLink which is a break for Go.
There was a problem hiding this comment.
update to PrivateLinks<PrivateLinkResource>
| enum ContainerRegistryResourceType { | ||
| `Microsoft.ContainerRegistry/registries`, | ||
| } |
…ion - JS-5780624 (#37095) Configurations: 'specification/containerregistry/resource-manager/Microsoft.ContainerRegistry/RegistryTasks/tspconfig.yaml', API Version: 2025-03-01-preview, SDK Release Type: beta, and CommitSHA: '3f223d61b02c0496581dfb71c78104761b448d5e' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=5780624 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. **Release plan link:** [https://web.powerapps.com/apps/821ab569-ae60-420d-8264-d7b5d5ef734c?release-plan-id=2a608315-60f6-f011-8406-000d3a376cbb](https://web.powerapps.com/apps/821ab569-ae60-420d-8264-d7b5d5ef734c?release-plan-id=2a608315-60f6-f011-8406-000d3a376cbb) **Submitted by**: clarkporter@microsoft.com ## Release Plan Details - Release Plan: https://aka.ms/sdk-release-planner?release-plan-id=2a608315-60f6-f011-8406-000d3a376cbb Spec pull request: Azure/azure-rest-api-specs#37169 Spec API version: 2025-03-01-preview --------- Co-authored-by: Clark Porter <CaPorter01@gmail.com> Co-authored-by: kazrael2119 <98569699+kazrael2119@users.noreply.github.com>
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.