Update SecurityPatch Description in 05-02preview to match stable version #29530
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 MergeNext steps that must be taken to merge this PR:
|
Swagger Validation Report
|
| Compared specs (v0.10.9) | new version | base version |
|---|---|---|
| managedClusters.json | 2024-05-02-preview(56bbf8a) | 2024-02-01(main) |
| managedClusters.json | 2024-05-02-preview(56bbf8a) | 2024-04-02-preview(main) |
The following breaking changes are detected by comparison with the latest stable version:
The following breaking changes are detected by comparison with the latest preview version:
| Rule | Message |
|---|---|
| The new version is missing a path that was found in the old version. Was path '/subscriptions/{subscriptionId}/providers/Microsoft.ContainerService/locations/{location}/osOptions/default' removed or restructured? Old: aks/preview/2024-04-02-preview/managedClusters.json#L73:5 |
|
| The '$ref' property points to different models in the old and new versions. New: aks/preview/2024-05-02-preview/managedClusters.json#L6521:9 Old: aks/preview/2024-04-02-preview/managedClusters.json#L6563:9 |
|
| The '$ref' property points to different models in the old and new versions. New: aks/preview/2024-05-02-preview/managedClusters.json#L6977:9 Old: aks/preview/2024-04-02-preview/managedClusters.json#L7014:9 |
|
| The new version has a different type 'array' than the previous one 'object'. New: aks/preview/2024-05-02-preview/managedClusters.json#L6521:9 Old: aks/preview/2024-04-02-preview/managedClusters.json#L6563:9 |
|
| The new version has a different type 'array' than the previous one 'object'. New: aks/preview/2024-05-02-preview/managedClusters.json#L6977:9 Old: aks/preview/2024-04-02-preview/managedClusters.json#L7014:9 |
|
| The new version is missing a property found in the old version. Was 'kubernetesVersion' renamed or removed? Old: aks/preview/2024-04-02-preview/managedClusters.json#L10082:7 |
|
| The new version is missing a property found in the old version. Was 'components' renamed or removed? Old: aks/preview/2024-04-02-preview/managedClusters.json#L10082:7 |
️⚠️LintDiff: 0 Warnings warning [Detail]
| Compared specs (v2.2.2) | new version | base version |
|---|---|---|
| package-preview-2024-05 | package-preview-2024-05(56bbf8a) | package-preview-2024-05(FumingZhang-containerservice-Microsoft.ContainerService-2024-05-02-preview) |
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-05-02-preview/managedClusters.json#L52 |
|
Operations API path must follow the schema provided in the common types. Location: aks/preview/2024-05-02-preview/managedClusters.json#L53 |
|
x-ms-pageable extension must be specified for LIST APIs.Location: aks/preview/2024-05-02-preview/managedClusters.json#L74 |
|
Get endpoints for collections of resources must only have the value and nextLink properties in their model.Location: aks/preview/2024-05-02-preview/managedClusters.json#L95 |
|
The resource name parameter 'roleName' should be defined with a 'pattern' restriction. Location: aks/preview/2024-05-02-preview/managedClusters.json#L236 |
|
server-fqdn is a query parameter. Post operation must not contain any query parameter other than api-version. Location: aks/preview/2024-05-02-preview/managedClusters.json#L294 |
|
server-fqdn is a query parameter. Post operation must not contain any query parameter other than api-version. Location: aks/preview/2024-05-02-preview/managedClusters.json#L339 |
|
format is a query parameter. Post operation must not contain any query parameter other than api-version. Location: aks/preview/2024-05-02-preview/managedClusters.json#L339 |
|
server-fqdn is a query parameter. Post operation must not contain any query parameter other than api-version. Location: aks/preview/2024-05-02-preview/managedClusters.json#L387 |
|
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: aks/preview/2024-05-02-preview/managedClusters.json#L527 |
|
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-05-02-preview/managedClusters.json#L634 |
|
The patch operation body parameter schema should contain property 'identity'. Location: aks/preview/2024-05-02-preview/managedClusters.json#L653 |
|
The async patch operation should return 202. Location: aks/preview/2024-05-02-preview/managedClusters.json#L671 |
|
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: aks/preview/2024-05-02-preview/managedClusters.json#L681 |
|
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: aks/preview/2024-05-02-preview/managedClusters.json#L739 |
|
The resource name parameter 'configName' should be defined with a 'pattern' restriction. Location: aks/preview/2024-05-02-preview/managedClusters.json#L799 |
|
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-05-02-preview/managedClusters.json#L969 |
|
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: aks/preview/2024-05-02-preview/managedClusters.json#L1013 |
|
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: aks/preview/2024-05-02-preview/managedClusters.json#L1181 |
|
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: aks/preview/2024-05-02-preview/managedClusters.json#L1308 |
|
x-ms-pageable extension must be specified for LIST APIs.Location: aks/preview/2024-05-02-preview/managedClusters.json#L1523 |
|
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-05-02-preview/managedClusters.json#L1527 |
|
Get endpoints for collections of resources must only have the value and nextLink properties in their model.Location: aks/preview/2024-05-02-preview/managedClusters.json#L1547 |
|
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-05-02-preview/managedClusters.json#L1566 |
|
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: aks/preview/2024-05-02-preview/managedClusters.json#L1612 |
|
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-05-02-preview/managedClusters.json#L1628 |
|
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: aks/preview/2024-05-02-preview/managedClusters.json#L1675 |
|
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-05-02-preview/managedClusters.json#L1691 |
|
Error response content of long running operations must follow the error schema provided in the common types v2 and above. Location: aks/preview/2024-05-02-preview/managedClusters.json#L1732 |
|
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-05-02-preview/managedClusters.json#L1748 |
️️✔️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.
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
️️✔️Automated merging requirements met succeeded [Detail] [Expand]
Swagger Generation Artifacts
|
Generated ApiView
|
matthchr
approved these changes
Jun 20, 2024
This was referenced Jun 20, 2024
FumingZhang
merged commit a6511bb
into
Azure:FumingZhang-containerservice-Microsoft.ContainerService-2024-05-02-preview
23 of 29 checks passed
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.write accessper aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext 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.