MFE April 2023 staging #23164
Merged
MFE April 2023 staging #23164
Conversation
This file contains 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
|
Hi, @kseager Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. vscswagger@microsoft.com |
Swagger Validation Report
|
| compared swaggers (via Oad v0.10.4)] | new version | base version |
|---|---|---|
| machineLearningServices.json | 2023-04-01(668499f) | 2022-10-01(main) |
| machineLearningServices.json | 2023-04-01(668499f) | 2023-02-01-preview(main) |
| workspaceFeatures.json | 2023-04-01(668499f) | 2022-10-01(main) |
| workspaceFeatures.json | 2023-04-01(668499f) | 2023-02-01-preview(main) |
The following breaking changes are detected by comparison with the latest stable version:
Only 17 items are listed, please refer to log for more details.
The following breaking changes are detected by comparison with the latest preview version:
Only 17 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
|
"new":"https://github.com/Azure/azure-rest-api-specs/blob/668499f066e856b2f29a1fb815eed498da0e63b6/specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json", "old":"https://github.com/Azure/azure-rest-api-specs/blob/main/specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-02-01-preview/mfe.json", "details":"Command failed: node "/mnt/vss/_work/_tasks/AzureApiValidation_5654d05d-82c1-48da-ad8f-161b817f6d41/0.0.49/common/temp/node_modules/.pnpm/@Azure+oad@0.10.4/node_modules/autorest/dist/app.js" --v2 --input-file=specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json --output-artifact=swagger-document.json --output-artifact=swagger-document.map --output-file=new --output-folder=/tmp\nERROR: Schema violation: Data does not match any schemas from 'oneOf'\n - file:///mnt/vss/_work/1/azure-rest-api-specs/specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json:8840:10 ($.paths["/subscriptions/subscriptionId/resourceGroups/resourceGroupName/providers/Microsoft.MachineLearningServices/workspaces/workspaceName/schedules/name"].delete["x-ms-examples"]["Delete Schedule."])\nERROR: Schema violation: Data does not match any schemas from 'oneOf'\n - file:///mnt/vss/_work/1/azure-rest-api-specs/spe" |
| The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearningServices/workspaces/{workspaceName}/computes/{computeName}/customServices' removed or restructured? Old: Microsoft.MachineLearningServices/preview/2023-02-01-preview/machineLearningServices.json#L1016:5 |
|
| The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearningServices/workspaces/{workspaceName}/computes/{computeName}/updateIdleShutdownSetting' removed or restructured? Old: Microsoft.MachineLearningServices/preview/2023-02-01-preview/machineLearningServices.json#L1340:5 |
|
| The new version is missing a definition that was found in the old version. Was 'EncryptionUpdateProperties' removed or renamed? New: Microsoft.MachineLearningServices/stable/2023-04-01/machineLearningServices.json#L1978:3 Old: Microsoft.MachineLearningServices/preview/2023-02-01-preview/machineLearningServices.json#L2109:3 |
|
| The new version is missing a definition that was found in the old version. Was 'EncryptionKeyVaultUpdateProperties' removed or renamed? New: Microsoft.MachineLearningServices/stable/2023-04-01/machineLearningServices.json#L1978:3 Old: Microsoft.MachineLearningServices/preview/2023-02-01-preview/machineLearningServices.json#L2109:3 |
|
| The new version is missing a definition that was found in the old version. Was 'ComputeInstanceAutologgerSettings' removed or renamed? New: Microsoft.MachineLearningServices/stable/2023-04-01/machineLearningServices.json#L1978:3 Old: Microsoft.MachineLearningServices/preview/2023-02-01-preview/machineLearningServices.json#L2109:3 |
|
| The new version is missing a definition that was found in the old version. Was 'WorkspaceConnectionAccessKey' removed or renamed? New: Microsoft.MachineLearningServices/stable/2023-04-01/machineLearningServices.json#L1978:3 Old: Microsoft.MachineLearningServices/preview/2023-02-01-preview/machineLearningServices.json#L2109:3 |
|
| The new version is missing a definition that was found in the old version. Was 'AccessKeyAuthTypeWorkspaceConnectionProperties' removed or renamed? New: Microsoft.MachineLearningServices/stable/2023-04-01/machineLearningServices.json#L1978:3 Old: Microsoft.MachineLearningServices/preview/2023-02-01-preview/machineLearningServices.json#L2109:3 |
|
| The new version is missing a definition that was found in the old version. Was 'WorkspaceConnectionServicePrincipal' removed or renamed? New: Microsoft.MachineLearningServices/stable/2023-04-01/machineLearningServices.json#L1978:3 Old: Microsoft.MachineLearningServices/preview/2023-02-01-preview/machineLearningServices.json#L2109:3 |
|
| The new version is missing a definition that was found in the old version. Was 'ServicePrincipalAuthTypeWorkspaceConnectionProperties' removed or renamed? New: Microsoft.MachineLearningServices/stable/2023-04-01/machineLearningServices.json#L1978:3 Old: Microsoft.MachineLearningServices/preview/2023-02-01-preview/machineLearningServices.json#L2109:3 |
|
| The new version is missing a definition that was found in the old version. Was 'FeatureStoreSettings' removed or renamed? New: Microsoft.MachineLearningServices/stable/2023-04-01/machineLearningServices.json#L1978:3 Old: Microsoft.MachineLearningServices/preview/2023-02-01-preview/machineLearningServices.json#L2109:3 |
|
| The new version is missing a definition that was found in the old version. Was 'ComputeRuntimeDto' removed or renamed? New: Microsoft.MachineLearningServices/stable/2023-04-01/machineLearningServices.json#L1978:3 Old: Microsoft.MachineLearningServices/preview/2023-02-01-preview/machineLearningServices.json#L2109:3 |
|
| The new version is missing a definition that was found in the old version. Was 'RecurrenceTrigger' removed or renamed? New: Microsoft.MachineLearningServices/stable/2023-04-01/machineLearningServices.json#L1978:3 Old: Microsoft.MachineLearningServices/preview/2023-02-01-preview/machineLearningServices.json#L2109:3 |
|
| The new version is missing a definition that was found in the old version. Was 'CronTrigger' removed or renamed? New: Microsoft.MachineLearningServices/stable/2023-04-01/machineLearningServices.json#L1978:3 Old: Microsoft.MachineLearningServices/preview/2023-02-01-preview/machineLearningServices.json#L2109:3 |
|
| The new version is missing a client parameter that was found in the old version. Was 'WorkspaceKindParameter' removed or renamed? New: Microsoft.MachineLearningServices/stable/2023-04-01/machineLearningServices.json#L1869:3 Old: Microsoft.MachineLearningServices/preview/2023-02-01-preview/machineLearningServices.json#L1984:3 |
|
| The new version is missing a client parameter that was found in the old version. Was 'WorkspaceForceToPurgeParameter' removed or renamed? New: Microsoft.MachineLearningServices/stable/2023-04-01/machineLearningServices.json#L1869:3 Old: Microsoft.MachineLearningServices/preview/2023-02-01-preview/machineLearningServices.json#L1984:3 |
|
| The '$ref' property points to different models in the old and new versions. New: Microsoft.MachineLearningServices/stable/2023-04-01/machineLearningServices.json#L5170:9 Old: Microsoft.MachineLearningServices/preview/2023-02-01-preview/machineLearningServices.json#L5382:9 |
️❌LintDiff: 25 Errors, 49 Warnings failed [Detail]
| compared tags (via openapi-validator v2.0.0) | new version | base version |
|---|---|---|
| package-2023-04 | package-2023-04(668499f) | package-2023-04(release-machinelearningservices-Microsoft.MachineLearningServices-2023-04-01) |
[must fix]The following errors/warnings are introduced by current PR:
Only 17 items are listed, please refer to log for more details.
| Rule | Message | Related RPC [For API reviewers] |
|---|---|---|
|
A 'delete' operation 'RegistryCodeContainers_Delete' with x-ms-long-running-operation extension must have a valid terminal success status code 200 or 204. Location: Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json#L64 |
RPC-Async-V1-01 |
|
An async PUT operation is tracked via Azure-AsyncOperation header. Set 'final-state-via' property to 'azure-async-operation' on 'x-ms-long-running-operation-options' Location: Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json#L191 |
RPC-Async-V1-01 |
|
A 'delete' operation 'RegistryCodeVersions_Delete' with x-ms-long-running-operation extension must have a valid terminal success status code 200 or 204. Location: Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json#L349 |
RPC-Async-V1-01 |
|
An async PUT operation is tracked via Azure-AsyncOperation header. Set 'final-state-via' property to 'azure-async-operation' on 'x-ms-long-running-operation-options' Location: Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json#L490 |
RPC-Async-V1-01 |
|
A 'delete' operation 'RegistryComponentContainers_Delete' with x-ms-long-running-operation extension must have a valid terminal success status code 200 or 204. Location: Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json#L706 |
RPC-Async-V1-01 |
|
An async PUT operation is tracked via Azure-AsyncOperation header. Set 'final-state-via' property to 'azure-async-operation' on 'x-ms-long-running-operation-options' Location: Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json#L833 |
RPC-Async-V1-01 |
|
A 'delete' operation 'RegistryComponentVersions_Delete' with x-ms-long-running-operation extension must have a valid terminal success status code 200 or 204. Location: Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json#L991 |
RPC-Async-V1-01 |
|
An async PUT operation is tracked via Azure-AsyncOperation header. Set 'final-state-via' property to 'azure-async-operation' on 'x-ms-long-running-operation-options' Location: Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json#L1132 |
RPC-Async-V1-01 |
|
A 'delete' operation 'RegistryDataContainers_Delete' with x-ms-long-running-operation extension must have a valid terminal success status code 200 or 204. Location: Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json#L1303 |
RPC-Async-V1-01 |
|
An async PUT operation is tracked via Azure-AsyncOperation header. Set 'final-state-via' property to 'azure-async-operation' on 'x-ms-long-running-operation-options' Location: Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json#L1428 |
RPC-Async-V1-01 |
|
A 'delete' operation 'RegistryDataVersions_Delete' with x-ms-long-running-operation extension must have a valid terminal success status code 200 or 204. Location: Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json#L1618 |
RPC-Async-V1-01 |
|
An async PUT operation is tracked via Azure-AsyncOperation header. Set 'final-state-via' property to 'azure-async-operation' on 'x-ms-long-running-operation-options' Location: Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json#L1757 |
RPC-Async-V1-01 |
|
A 'delete' operation 'RegistryEnvironmentContainers_Delete' with x-ms-long-running-operation extension must have a valid terminal success status code 200 or 204. Location: Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json#L1999 |
RPC-Async-V1-01 |
|
An async PUT operation is tracked via Azure-AsyncOperation header. Set 'final-state-via' property to 'azure-async-operation' on 'x-ms-long-running-operation-options' Location: Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json#L2126 |
RPC-Async-V1-01 |
|
A 'delete' operation 'RegistryEnvironmentVersions_Delete' with x-ms-long-running-operation extension must have a valid terminal success status code 200 or 204. Location: Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json#L2311 |
RPC-Async-V1-01 |
|
An async PUT operation is tracked via Azure-AsyncOperation header. Set 'final-state-via' property to 'azure-async-operation' on 'x-ms-long-running-operation-options' Location: Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json#L2452 |
RPC-Async-V1-01 |
|
A 'delete' operation 'RegistryModelContainers_Delete' with x-ms-long-running-operation extension must have a valid terminal success status code 200 or 204. Location: Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json#L2623 |
RPC-Async-V1-01 |
The following errors/warnings exist before current PR submission:
Only 17 items are listed, please refer to log for more details.
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️️✔️CadlAPIView succeeded [Detail] [Expand]
️️✔️TypeSpecAPIView succeeded [Detail] [Expand]
️❌ModelValidation: 6 Errors, 0 Warnings failed [Detail]
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
️️✔️TypeSpec Validation succeeded [Detail] [Expand]
Validation passes for TypeSpec Validation.
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
Swagger Generation Artifacts
|
Generated ApiView
|
openapi-workflow-bot
bot
added
ARMReview
WaitForARMFeedback
|
Hi, @kseager your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
AzureRestAPISpecReview
added
BreakingChangeReviewRequired
|
Hi @kseager, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. |
|
Hi @kseager, Your PR has some issues. Please fix the CI sequentially by following the order of
|
|
This PR sounds similar to #23165 - what is the difference? are both needed? |
| @@ -1,14 +1,3416 @@ | |||
| { | |||
| "swagger": "2.0", | |||
| "info": { | |||
| "title": "Azure Machine Learning Workspaces", | |||
| "title": "Azure Machine Learning Services", | |||
There was a problem hiding this comment.
this change is making the Go SDK generation to fail.
Could we revert this on this PR and introduce this change in a clean PR and resolve any issues related with this on that PR?
There was a problem hiding this comment.
created alignment between RPs to fix this
custom-words.txt
Outdated
| @@ -2752,4 +2752,4 @@ remediatable | |||
| Overprovisioning | |||
| Unprepares | |||
| Unpreparing | |||
|
|
|||
| wasbs | |||
There was a problem hiding this comment.
What is this? Do we need it? #Resolved
There was a problem hiding this comment.
it's an acronym for Windows Azure Storage Blob, I need it otherwise I get flagged for a misspelling, but I believe it is valid since it's a valid acronym. Let me know if I should handle this scenario differently.
Can we rename this to anything else that wouldn't use unfamiliar acronyms? Like secureBlobFileSystemUri? blobFileSystemUri? In reply to: 1476531843 Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json:15943 in c9cc39f. [](commit_id = c9cc39f92468fa8517b51929ec124a1a8f7ac6c4, deletion_comment = False) |
| "property1": "string", | ||
| "property2": "string" | ||
| } | ||
| }, |
There was a problem hiding this comment.
why is tags inside of properties? This isn't normal
There was a problem hiding this comment.
Can you please address this?
| "type": "Microsoft.MachineLearningServices/registries/codes", | ||
| "properties": { | ||
| "description": "string", | ||
| "tags": { |
There was a problem hiding this comment.
ok to answer this question and the question above, we have a legacy exception to use tags at the property level. But it's only for our "assets"-code/model/etc and job types
There was a problem hiding this comment.
ARm will not be able to use these tags I dont think policy etc will work with this scheme
There was a problem hiding this comment.
Please address the latest response.
This name doesn't work as a REST action because its not a verb. While you're making breaking changes here, can you fix this? e.g. instead of should be POST /registerPendingUpload or In reply to: 1476540613 In reply to: 1476540613 Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/stable/2023-04-01/mfe.json:3339 in 1720062. [](commit_id = 172006293c6843acb8293d5a04d91f38f1bf35f4, deletion_comment = False) |
ArcturusZhang
approved these changes
Apr 2, 2023
added 21 commits
April 2, 2023 18:43
… the final object post-polling
kseager
force-pushed
the
kaseager-april-2023-staging
branch
from
9673c13 to
37b77be
Compare
|
Suppress the lintdiff errors since ARM has signed off |
ArcturusZhang
merged commit cf237c6
into
Azure:release-machinelearningservices-Microsoft.MachineLearningServices-2023-04-01
ArcturusZhang
pushed a commit
that referenced
this pull request
Apr 18, 2023
…023 04 01 (#23450) * Adds base for updating Microsoft.MachineLearningServices from version stable/2022-10-01 to version 2023-04-01 * Updates readme * Updates API version in new specs and examples * [Stable] Bring Back schedule shutdown MLC models (#23039) * bring back schedule shutdown MLC models * add description --------- Co-authored-by: Naman Agarwal <naagarw@microsoft.com> * add minLength:1 prop to required strings (#23109) * [Stable] Add IdleShutdown properties and api (#23042) * [Stable] Add IdleShutdown properties and api * update version * remove api to update IdleShutdownSetting * Delete example --------- Co-authored-by: Naman Agarwal <naagarw@microsoft.com> * Pushing new features in stable swagger (#23071) * Pushing new features in stable swagger * Added example file * Triggering retest * Fixed version issue * Triggering retest * Removing OS Patching * Changes as per feedback, and add os patching back * Fix formatting * Removed Custom Service Update API * Fixed Example Files * Added as per review comments * Added as per review comments * Retrigger test --------- Co-authored-by: Srivatsa Sinha <srsinha@microsoft.com> * Add Registries 2023-04-01 Swagger (#23085) * add swagger + examples * fix readme * fix readme * switching to autogenerated registries swagger * fix spellcheck * update ga examples * previous API version for comparison = 2023-02-01-preview * new API version for comparison = 2023-04-01 * update examples * update swagger, examples to fix pr gates * fix lint diff errors * delete should have a 202 response, update createorupdate examples, fix removeRegions operation * removeRegions -> LRO POST operation * fix LRO options on removeRegions * add registryNameParamert * update swagger * update * PATCH property should have sku, identity properties * fix example --------- Co-authored-by: Komal Yadav <komalyadav@microsoft.com> * MFE April 2023 staging (#23164) * add latest mfe.json * updated examples * add wasbs to known words * swap pendingupload to proper naming * align RPs on Azure Machine Learning Services * rename pendingUpload to verb: startPendingUpload * remove trailing slash startpendingupload * improve descriptions * add pattern to all resource name types + examples * update original-uri -> azure-async-operation * remove wasbs and mark credential usage as secret * test is changing all to azure-async-operation causes breaking change * the code is implemented where the original-uri is where you will find the final object post-polling * update examples to remove wasbsUri * reference registries instead for RegistryName * remove wasbs * original-uri -> azure-async-operation * update examples to empty secrets * CreateOrUpdatePendingUpload -> CreateOrUpdateStartPendingUpload * add pattern for workspaceName * x-ms-secret on the SASUri * switch back to original-uri given update from auto-rest folks --------- Co-authored-by: Kayla Ames <kaseager@microsoft.com> * update compute examples to ReadOnly * v5->v3 * PartialManagedServiceIdentity -> RegistryPartialManagedServiceIdentity * update ID for delete/cancel job/schedule location header * PrivateEndpointConnection -> RegistryPrivateEndpointConnection * more renames for Registry * align mlc with arm * update registry examples * update registryPrivateLinkServiceConnectionState in examples * update description arm id for registryPrivateEndpointConnections * update to preview --------- Co-authored-by: Naman Agarwal <namanag16@gmail.com> Co-authored-by: Naman Agarwal <naagarw@microsoft.com> Co-authored-by: Teddy Todorov <thtodoro@microsoft.com> Co-authored-by: srivatsasinha <102133347+srivatsasinha@users.noreply.github.com> Co-authored-by: Srivatsa Sinha <srsinha@microsoft.com> Co-authored-by: Komal Yadav <23komal.yadav23@gmail.com> Co-authored-by: Komal Yadav <komalyadav@microsoft.com> Co-authored-by: Kayla Ames <kaseager@microsoft.com>
JoshLove-msft
pushed a commit
to JoshLove-msft/azure-rest-api-specs
that referenced
this pull request
Apr 25, 2023
…023 04 01 (Azure#23450) * Adds base for updating Microsoft.MachineLearningServices from version stable/2022-10-01 to version 2023-04-01 * Updates readme * Updates API version in new specs and examples * [Stable] Bring Back schedule shutdown MLC models (Azure#23039) * bring back schedule shutdown MLC models * add description --------- Co-authored-by: Naman Agarwal <naagarw@microsoft.com> * add minLength:1 prop to required strings (Azure#23109) * [Stable] Add IdleShutdown properties and api (Azure#23042) * [Stable] Add IdleShutdown properties and api * update version * remove api to update IdleShutdownSetting * Delete example --------- Co-authored-by: Naman Agarwal <naagarw@microsoft.com> * Pushing new features in stable swagger (Azure#23071) * Pushing new features in stable swagger * Added example file * Triggering retest * Fixed version issue * Triggering retest * Removing OS Patching * Changes as per feedback, and add os patching back * Fix formatting * Removed Custom Service Update API * Fixed Example Files * Added as per review comments * Added as per review comments * Retrigger test --------- Co-authored-by: Srivatsa Sinha <srsinha@microsoft.com> * Add Registries 2023-04-01 Swagger (Azure#23085) * add swagger + examples * fix readme * fix readme * switching to autogenerated registries swagger * fix spellcheck * update ga examples * previous API version for comparison = 2023-02-01-preview * new API version for comparison = 2023-04-01 * update examples * update swagger, examples to fix pr gates * fix lint diff errors * delete should have a 202 response, update createorupdate examples, fix removeRegions operation * removeRegions -> LRO POST operation * fix LRO options on removeRegions * add registryNameParamert * update swagger * update * PATCH property should have sku, identity properties * fix example --------- Co-authored-by: Komal Yadav <komalyadav@microsoft.com> * MFE April 2023 staging (Azure#23164) * add latest mfe.json * updated examples * add wasbs to known words * swap pendingupload to proper naming * align RPs on Azure Machine Learning Services * rename pendingUpload to verb: startPendingUpload * remove trailing slash startpendingupload * improve descriptions * add pattern to all resource name types + examples * update original-uri -> azure-async-operation * remove wasbs and mark credential usage as secret * test is changing all to azure-async-operation causes breaking change * the code is implemented where the original-uri is where you will find the final object post-polling * update examples to remove wasbsUri * reference registries instead for RegistryName * remove wasbs * original-uri -> azure-async-operation * update examples to empty secrets * CreateOrUpdatePendingUpload -> CreateOrUpdateStartPendingUpload * add pattern for workspaceName * x-ms-secret on the SASUri * switch back to original-uri given update from auto-rest folks --------- Co-authored-by: Kayla Ames <kaseager@microsoft.com> * update compute examples to ReadOnly * v5->v3 * PartialManagedServiceIdentity -> RegistryPartialManagedServiceIdentity * update ID for delete/cancel job/schedule location header * PrivateEndpointConnection -> RegistryPrivateEndpointConnection * more renames for Registry * align mlc with arm * update registry examples * update registryPrivateLinkServiceConnectionState in examples * update description arm id for registryPrivateEndpointConnections * update to preview --------- Co-authored-by: Naman Agarwal <namanag16@gmail.com> Co-authored-by: Naman Agarwal <naagarw@microsoft.com> Co-authored-by: Teddy Todorov <thtodoro@microsoft.com> Co-authored-by: srivatsasinha <102133347+srivatsasinha@users.noreply.github.com> Co-authored-by: Srivatsa Sinha <srsinha@microsoft.com> Co-authored-by: Komal Yadav <23komal.yadav23@gmail.com> Co-authored-by: Komal Yadav <komalyadav@microsoft.com> Co-authored-by: Kayla Ames <kaseager@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo. If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist (MS Employees Only):
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.
Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.