-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Goutham mn redhatopenshift microsoft.red hat open shift 2023 09 04 #25711
Goutham mn redhatopenshift microsoft.red hat open shift 2023 09 04 #25711
Conversation
…2023-04-01 to version 2023-09-04
Next Steps to Merge✔️ All automated merging requirements have been met! Refer to step 4 in the PR workflow diagram (even if your PR is for data plane, not ARM). |
Swagger Validation Report
|
compared swaggers (via Oad v0.10.4)] | new version | base version |
---|---|---|
redhatopenshift.json | 2023-09-04(43cd5b5) | 2023-04-01(main) |
redhatopenshift.json | 2023-09-04(43cd5b5) | 2023-07-01-preview(main) |
The following breaking changes are detected by comparison with the latest stable version:
Rule | Message |
---|---|
1023 - TypeFormatChanged |
The new version has a different format than the previous one. New: Microsoft.RedHatOpenShift/stable/2023-09-04/redhatopenshift.json#L2512:9 Old: Microsoft.RedHatOpenShift/stable/2023-04-01/redhatopenshift.json#L2483:9 |
1023 - TypeFormatChanged |
The new version has a different format than the previous one. New: Microsoft.RedHatOpenShift/stable/2023-09-04/redhatopenshift.json#L2521:9 Old: Microsoft.RedHatOpenShift/stable/2023-04-01/redhatopenshift.json#L2491:9 |
1048 - AddedXmsEnum |
The new version adds a x-ms-enum extension. New: Microsoft.RedHatOpenShift/stable/2023-09-04/redhatopenshift.json#L2068:9 Old: Microsoft.RedHatOpenShift/stable/2023-04-01/redhatopenshift.json#L2064:9 |
1048 - AddedXmsEnum |
The new version adds a x-ms-enum extension. New: Microsoft.RedHatOpenShift/stable/2023-09-04/redhatopenshift.json#L2252:5 Old: Microsoft.RedHatOpenShift/stable/2023-04-01/redhatopenshift.json#L2227:5 |
The following breaking changes are detected by comparison with the latest preview version:
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️
LintDiff succeeded [Detail] [Expand]
Validation passes for LintDiff.
compared tags (via openapi-validator v2.1.5) | new version | base version |
---|---|---|
package-2023-09-04 | package-2023-09-04(43cd5b5) | default(main) |
️️✔️
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.
️️✔️
PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
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
|
Generated ApiView
|
Hi @gouthamMN! For review efficiency consideration, when creating a new API version, it is required to place API specs of the base version in the first commit, and push new version updates into successive commits. You can use OpenAPIHub to initialize the PR for adding a new version. |
Please address or respond to feedback from the ARM API reviewer. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left comment. We'll need breaking change review as well as review from ARM team on this. Azure SDK check has been failing for some time so is not expected to pass at the moment AFAIK.
/azp run unifiedPipeline |
No pipelines are associated with this pull request. |
/pr RequestMerge |
/pr RequestMerge |
Swagger pipeline restarted successfully, please wait for status update in this comment. |
…25711) * Adds base for updating Microsoft.RedHatOpenShift from version stable/2023-04-01 to version 2023-09-04 * Updates readme * Updates API version in new specs and examples * add 2023-09-04 rest api specs * resolve LintDiff check failure * tag with full date * rename workerProfilesStatus to activeWorkerProfiles and add canceled provisioning state * fix lintDiff * Revert "tag with full date" This reverts commit cedd9ad. Revert the workerProfilesStatus and ProvisioningState changes * Revert "rename workerProfilesStatus to activeWorkerProfiles and add canceled provisioning state" This reverts commit d921e05. revert workerProfilesStatus and ProvisioningState changes * tag with full date * update readme --------- Co-authored-by: gniranjan <gniranjan@microsoft.com>
ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
[1] ARM review queue (for merge queues, see [4])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label
ARMChangesRequested
is removed from your PR. This should cause the label
WaitForARMFeedback
to be added.[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue (for ARM review queue, [1])
If you need further help with anything, see
Getting help
section below.Purpose of this PR
What's the purpose of this PR? Check all that apply. 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 Step 2, "ARM Review", for this PR.
Breaking changes review (Step 1)
you must follow the breaking changes process.
IMPORTANT This applies even if:
Such claims must be reviewed, and the process is the same.
ARM API changes review (Step 2)
ARMReview
label.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 ApiView
comment 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
Swagger-Suppression-Process
to get approval.
Getting help
and https://aka.ms/ci-fix.