update(acns): advanced networking profile to note addition costs #29146
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
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge. |
|
Hi @snguyen64, this service has enabled ShiftLeft Toolset. All spec updates MUST be initiated from service ADO project repo, so that to guarantee it to be the source of truth., please review this pull request if it is intentional or reject it if it is not expected. Normally, all the specification or example changes should start with PR created in ADO. |
Swagger Validation Report
|
| Compared specs (v0.10.9) | new version | base version |
|---|---|---|
| managedClusters.json | 2024-03-02-preview(16056d7) | 2024-03-02-preview(main) |
️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️LintDiff: 0 Warnings warning [Detail]
| Compared specs (v2.2.2) | new version | base version |
|---|---|---|
| package-preview-2024-03 | package-preview-2024-03(16056d7) | package-preview-2024-03(main) |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
|
The response schema of operations API '/providers/Microsoft.ContainerService/operations' does not match the ARM specification. Please standardize the schema. Location: aks/preview/2024-03-02-preview/managedClusters.json#L52 |
|
Operations API path must follow the schema provided in the common types. Location: aks/preview/2024-03-02-preview/managedClusters.json#L53 |
|
Query parameter resource-type should be removed. Point Get's MUST not have query parameters other than api version. Location: aks/preview/2024-03-02-preview/managedClusters.json#L80 |
|
x-ms-pageable extension must be specified for LIST APIs.Location: aks/preview/2024-03-02-preview/managedClusters.json#L116 |
|
Get endpoints for collections of resources must only have the value and nextLink properties in their model.Location: aks/preview/2024-03-02-preview/managedClusters.json#L137 |
|
The resource name parameter 'roleName' should be defined with a 'pattern' restriction. Location: aks/preview/2024-03-02-preview/managedClusters.json#L278 |
|
server-fqdn is a query parameter. Post operation must not contain any query parameter other than api-version. Location: aks/preview/2024-03-02-preview/managedClusters.json#L336 |
|
server-fqdn is a query parameter. Post operation must not contain any query parameter other than api-version. Location: aks/preview/2024-03-02-preview/managedClusters.json#L381 |
|
format is a query parameter. Post operation must not contain any query parameter other than api-version. Location: aks/preview/2024-03-02-preview/managedClusters.json#L381 |
|
server-fqdn is a query parameter. Post operation must not contain any query parameter other than api-version. Location: aks/preview/2024-03-02-preview/managedClusters.json#L429 |
|
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: aks/preview/2024-03-02-preview/managedClusters.json#L569 |
|
Long-running PATCH operations must have responses with 200, 202 and default return codes. They also must not have other response codes. Location: aks/preview/2024-03-02-preview/managedClusters.json#L676 |
|
The patch operation body parameter schema should contain property 'identity'. Location: aks/preview/2024-03-02-preview/managedClusters.json#L695 |
|
The async patch operation should return 202. Location: aks/preview/2024-03-02-preview/managedClusters.json#L713 |
|
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: aks/preview/2024-03-02-preview/managedClusters.json#L723 |
|
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: aks/preview/2024-03-02-preview/managedClusters.json#L781 |
|
The resource name parameter 'configName' should be defined with a 'pattern' restriction. Location: aks/preview/2024-03-02-preview/managedClusters.json#L841 |
|
Long-running POST operations must have responses with 202 and default return codes. They must also have a 200 return code if only if the final response is intended to have a schema, if not the 200 return code must not be specified. They also must not have other response codes. Location: aks/preview/2024-03-02-preview/managedClusters.json#L1011 |
|
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: aks/preview/2024-03-02-preview/managedClusters.json#L1055 |
|
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: aks/preview/2024-03-02-preview/managedClusters.json#L1223 |
|
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: aks/preview/2024-03-02-preview/managedClusters.json#L1347 |
|
x-ms-pageable extension must be specified for LIST APIs.Location: aks/preview/2024-03-02-preview/managedClusters.json#L1562 |
|
Per the Noun_Verb convention for Operation Ids, the noun 'AgentPools' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: aks/preview/2024-03-02-preview/managedClusters.json#L1566 |
|
Get endpoints for collections of resources must only have the value and nextLink properties in their model.Location: aks/preview/2024-03-02-preview/managedClusters.json#L1586 |
|
200 return code does not have a schema specified. LRO POST must have a 200 return code if only if the final response is intended to have a schema, if not the 200 return code must not be specified. Location: aks/preview/2024-03-02-preview/managedClusters.json#L1605 |
|
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: aks/preview/2024-03-02-preview/managedClusters.json#L1651 |
|
200 return code does not have a schema specified. LRO POST must have a 200 return code if only if the final response is intended to have a schema, if not the 200 return code must not be specified. Location: aks/preview/2024-03-02-preview/managedClusters.json#L1667 |
|
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: aks/preview/2024-03-02-preview/managedClusters.json#L1714 |
|
Long-running POST operations must have responses with 202 and default return codes. They must also have a 200 return code if only if the final response is intended to have a schema, if not the 200 return code must not be specified. They also must not have other response codes. Location: aks/preview/2024-03-02-preview/managedClusters.json#L1730 |
|
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: aks/preview/2024-03-02-preview/managedClusters.json#L1771 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️️✔️TypeSpecAPIView succeeded [Detail] [Expand]
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
️️✔️Automated merging requirements met succeeded [Detail] [Expand]
Swagger Generation Artifacts
|
openapi-workflow-bot
bot
added
ShiftLeftViolation
DoNotMerge
Generated ApiView
|
AzureRestAPISpecReview
added
ARMReview
ReadyForApiTest
This was referenced May 17, 2024
matthchr
approved these changes
May 18, 2024
snguyen64
force-pushed
the
retina-advanced-networking-api-update-2024-03-02-preview
branch
from
5f56037
to
30db5d1
Compare
gary-x-li
added
the
ARMSignedOff
openapi-pipeline-app
bot
removed
the
WaitForARMFeedback
|
/pr RequestMerge |
microsoft-github-policy-service
bot
added
the
MergeRequested
FumingZhang
removed
the
DoNotMerge
rkmanda
approved these changes
Jun 9, 2024
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 (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting helpsection at the bottom of this PR description.PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!
Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
Additional information
Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the
Generated ApiViewcomment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.
Getting help
Purpose of this PRandDue diligence checklist.Next Steps to Mergecomment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.