Add ContainerApp Start/Stop for 2023-04-01-preview #23497
Merged
+144
−0
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, @Zijian-Ju 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 |
|---|---|---|
| ContainerApps.json | 2023-04-01-preview(ae69010) | 2022-10-01(main) |
| ContainerApps.json | 2023-04-01-preview(ae69010) | 2022-11-01-preview(main) |
The following breaking changes are detected by comparison with the latest stable version:
| Rule | Message |
|---|---|
|
The new version is missing a property found in the old version. Was 'workloadProfileType' renamed or removed? New: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L681:11 Old: Microsoft.App/stable/2022-10-01/ContainerApps.json#L541:11 |
️❌LintDiff: 2 Errors, 2 Warnings failed [Detail]
| compared tags (via openapi-validator v2.0.0) | new version | base version |
|---|---|---|
| package-preview-2023-04 | package-preview-2023-04(ae69010) | package-preview-2023-04(release-app-Microsoft.App-2023-04-01-preview) |
[must fix]The following errors/warnings are introduced by current PR:
| Rule | Message | Related RPC [For API reviewers] |
|---|---|---|
|
An async POST operation is tracked via Azure-AsyncOperation header. Set 'final-state-via' property to 'location' on 'x-ms-long-running-operation-options' Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L488 |
RPC-Async-V1-11 |
|
An async POST operation is tracked via Azure-AsyncOperation header. Set 'final-state-via' property to 'location' on 'x-ms-long-running-operation-options' Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L544 |
RPC-Async-V1-11 |
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L494 |
||
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L550 |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
|
The resource name parameter 'containerAppName' should be defined with a 'pattern' restriction. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L99 |
|
The patch operation body parameter schema should not contains property name. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L296 |
|
The patch operation body parameter schema should not contains property type. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L296 |
|
The patch operation body parameter schema should not contains property location. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L296 |
|
Properties of a PATCH request body must not be required, property:location. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L301 |
|
The resource name parameter 'containerAppName' should be defined with a 'pattern' restriction. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L339 |
|
The resource name parameter 'containerAppName' should be defined with a 'pattern' restriction. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L391 |
|
The resource name parameter 'containerAppName' should be defined with a 'pattern' restriction. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L437 |
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L25 |
|
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L64 |
|
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L106 |
|
| The summary and description values should not be same. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L148 |
|
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L155 |
|
| The summary and description values should not be same. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L218 |
|
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L225 |
|
| The x-ms-long-running-operation-options should be specified explicitly to indicate the type of response header to track the async operation. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L275 |
|
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L282 |
|
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L346 |
|
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L398 |
|
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L444 |
|
| Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L681 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L789 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L840 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L855 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L905 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L1038 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L1153 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L1168 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L1238 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L1243 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️️✔️CadlAPIView succeeded [Detail] [Expand]
️️✔️TypeSpecAPIView succeeded [Detail] [Expand]
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️❌PrettierCheck: 1 Errors, 0 Warnings failed [Detail]
| Rule | Message |
|---|---|
|
Code style issues found path: preview/2023-04-01-preview/examples/ContainerApps_Stop.json |
️️✔️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
|
AzureRestAPISpecReview
added
ARMReview
BreakingChangeReviewRequired
|
Hi @Zijian-Ju, 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 @Zijian-Ju, Your PR has some issues. Please fix the CI sequentially by following the order of
|
|
Does it need arm review? Also why there is cross-version breaking changes? It seems not found this PR. |
…//github.com/Azure/azure-rest-api-specs into release-app-Microsoft.App-2023-04-01-preview
Zijian-Ju
force-pushed
the
zijian-ju/containerappStart
branch
from
d38df0a to
fd456ab
Compare
Hi @weidongxu-microsoft , thanks for taking reaction.
|
weidongxu-microsoft
added
the
WaitForARMFeedback
|
Please include the previous approval of the breaks. Or you can just request a new approval in this PR. |
Juliehzl
reviewed
Apr 18, 2023
.../resource-manager/Microsoft.App/preview/2023-04-01-preview/examples/ContainerApps_Start.json
Outdated
Show resolved
Hide resolved
Swagger Validation Report
|
| compared swaggers (via Oad v0.10.4)] | new version | base version |
|---|---|---|
| ContainerApps.json | 2023-04-01-preview(df755b5) | 2022-10-01(main) |
| ContainerApps.json | 2023-04-01-preview(df755b5) | 2022-11-01-preview(main) |
The following breaking changes are detected by comparison with the latest stable version:
| Rule | Message |
|---|---|
|
The new version is missing a property found in the old version. Was 'workloadProfileType' renamed or removed? New: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L681:11 Old: Microsoft.App/stable/2022-10-01/ContainerApps.json#L541:11 |
️⚠️LintDiff: 2 Warnings warning [Detail]
| compared tags (via openapi-validator v2.0.0) | new version | base version |
|---|---|---|
| package-preview-2023-04 | package-preview-2023-04(df755b5) | package-preview-2023-04(release-app-Microsoft.App-2023-04-01-preview) |
[must fix]The following errors/warnings are introduced by current PR:
| Rule | Message | Related RPC [For API reviewers] |
|---|---|---|
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L494 |
||
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L550 |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
|
The resource name parameter 'containerAppName' should be defined with a 'pattern' restriction. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L99 |
|
The patch operation body parameter schema should not contains property name. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L296 |
|
The patch operation body parameter schema should not contains property type. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L296 |
|
The patch operation body parameter schema should not contains property location. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L296 |
|
Properties of a PATCH request body must not be required, property:location. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L301 |
|
The resource name parameter 'containerAppName' should be defined with a 'pattern' restriction. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L339 |
|
The resource name parameter 'containerAppName' should be defined with a 'pattern' restriction. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L391 |
|
The resource name parameter 'containerAppName' should be defined with a 'pattern' restriction. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L437 |
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L25 |
|
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L64 |
|
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L106 |
|
| The summary and description values should not be same. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L148 |
|
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L155 |
|
| The summary and description values should not be same. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L218 |
|
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L225 |
|
| The x-ms-long-running-operation-options should be specified explicitly to indicate the type of response header to track the async operation. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L275 |
|
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L282 |
|
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L346 |
|
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L398 |
|
| Parameter 'api-version' is referenced but not defined in the global parameters section of Service Definition Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L444 |
|
| Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L681 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L789 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L840 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L855 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L905 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L1038 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L1153 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L1168 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L1238 |
|
| Booleans properties are not descriptive in all cases and can make them to use, evaluate whether is makes sense to keep the property as boolean or turn it into an enum. Location: Microsoft.App/preview/2023-04-01-preview/ContainerApps.json#L1243 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️️✔️CadlAPIView succeeded [Detail] [Expand]
️️✔️TypeSpecAPIView succeeded [Detail] [Expand]
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️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.
Hi, there seems a conflict when I change the "final-state-via" to "azure-async-operation", the Swagger LintDiff is asking to use "Location" as the "final-state-via" while the [Staging] Swagger LintDiff is asking to use "azure-async-operation". Which one should I follow in this case? Thanks |
AzureRestAPISpecReview
removed
the
BreakingChangeReviewRequired
@weidongxu-microsoft could you help clarify? According to #23497 (comment), location header is correct for POST async API |
AzureRestAPISpecReview
added
the
BreakingChangeReviewRequired
For |
|
Hi @weidongxu-microsoft , the breaking change is introduced in an earlier API version 2022-11-01-preview and has been approved (attached) https://msazure.visualstudio.com/One/_workitems/edit/16986590. It is unrelated to this change. |
|
Breaking change review item is created: https://msazure.visualstudio.com/One/_workitems/edit/19310933/ |
|
Breaking change previously reviewed/approved in #22896 |
mikekistler
added
the
Approved-BreakingChange
|
Hi @sjanamma , it has been approved by breaking change team, could you please continue the process? thanks |
zhenqxuMSFT
approved these changes
May 6, 2023
sjanamma
removed
the
ARMChangesRequested
openapi-workflow-bot
bot
added
the
WaitForARMFeedback
sjanamma
added
the
ARMSignedOff
openapi-workflow-bot
bot
removed
the
WaitForARMFeedback
specification/app/resource-manager/Microsoft.App/preview/2023-04-01-preview/ContainerApps.json
Show resolved
Hide resolved
specification/app/resource-manager/Microsoft.App/preview/2023-04-01-preview/ContainerApps.json
Show resolved
Hide resolved
|
I am leaving this PR as ARMSignedOff, as no ARM level concerns. |
weidongxu-microsoft
approved these changes
May 12, 2023
weidongxu-microsoft
merged commit b80ac0f
into
Azure:release-app-Microsoft.App-2023-04-01-preview
tadelesh
pushed a commit
that referenced
this pull request
May 26, 2023
* Adds base for updating Microsoft.App from version preview/2022-11-01-preview to version 2023-04-01-preview * Updates readme * Updates API version in new specs and examples * support terminationGracePeriodSeconds (#23476) * Support SubPath in volume mount and mount options for azure file volume (#23496) * Support SubPath in volume mount and mount options for azure file volume * update description * Add replica/container running state (#23617) * add replica/container running state * spell error fix * add event trigger for Container Jobs 2023-04-01-preview (#23724) * add event trigger for Container Jobs 2023-04-01-preview * prettier and avocado fix --------- Co-authored-by: Taher Darolywala <tdarolywala@microsoft.com> * Resolve Comments for Event driven jobs (#23729) * Resolve Comments for Event driven jobs * change scaling rule to azure-servicebus * update example --------- Co-authored-by: Taher Darolywala <tdarolywala@microsoft.com> * Swagger change for mtls and runningState (#23767) * 1. Add mtls properties for managed ManagedEnvironment 2. Add running state for Revision * fix * Add ContainerApp Start/Stop for 2023-04-01-preview (#23497) * Add ContainerApp Start/Stop for 2023-04-01-preview * Fix validation error * Fix validation error * Change example to add location in header * Fix lint error * Fix lint issue * Fix lint issue * Fix lint issue * Fix lint issue * Fix lint issue * Fix lint issue * Fix lint issue * Fix lint issue * Add new source controls properties (#23891) * Add new source controls properties * Update examples * fix examples * Change event trigger replica properties to executions, add polling in… (#23810) * Change event trigger replica properties to executions, add polling interval to event trigger, fix typos and descriptions to accommodate both apps and jobs * Fix validation errors * code review comments * Fix formatting errors * Code review comments * Add single execution history endpoint, refactor copy paste code for j… (#23816) * Add single execution history endpoint, refactor copy paste code for jobName and jobExecutionName path parameters * Fix validation errors from ARM * Fix validation errors * Code review comments * Fix validation error * code review comments from Anand * Add springboard properties (#23932) * Add springboard properties * CR comments * Update specification/app/resource-manager/Microsoft.App/preview/2023-04-01-preview/examples/ContainerApps_CreateOrUpdate.json Co-authored-by: Jitin John <jijohn@microsoft.com> * Update specification/app/resource-manager/Microsoft.App/preview/2023-04-01-preview/examples/ContainerApps_CreateOrUpdate.json Co-authored-by: Jitin John <jijohn@microsoft.com> --------- Co-authored-by: Jitin John <jijohn@microsoft.com> * Fix Lint issues in ContainerApps.json (#24107) * Fix lint issue * Fix format issue * Fix json format issue * Fix model validation * Fix lint error * fix param (#24166) Co-authored-by: Chenghui Yu <chenghuiyu@microsoft.com> --------- Co-authored-by: Zunli Hu <zuh@microsoft.com> Co-authored-by: njucz <740360112@qq.com> Co-authored-by: LaylaLiu-gmail <38268900+LaylaLiu-gmail@users.noreply.github.com> Co-authored-by: Xingjian Wang <79332479+xwang971@users.noreply.github.com> Co-authored-by: Taher Daroly <41846928+tdaroly@users.noreply.github.com> Co-authored-by: Taher Darolywala <tdarolywala@microsoft.com> Co-authored-by: zhenqxuMSFT <zhenqxu@microsoft.com> Co-authored-by: Zijian-Ju <53360473+Zijian-Ju@users.noreply.github.com> Co-authored-by: Sanchit Mehta <sanchit.mehta602@gmail.com> Co-authored-by: trajkobal <108365738+trajkobal@users.noreply.github.com> Co-authored-by: Ahmed ElSayed <ahmed@elsayed.io> Co-authored-by: Jitin John <jijohn@microsoft.com> Co-authored-by: Seris370 <38371667+Seris370@users.noreply.github.com> Co-authored-by: Chenghui Yu <chenghuiyu@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.