-
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
Add Azure Red Hat OpenShift 2024-08-12-preview API version #30004
Open
cadenmarchese
wants to merge
7
commits into
Azure:main
Choose a base branch
from
cadenmarchese:add-20240812preview-2
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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:
|
Generated ApiView
|
This was referenced Jul 29, 2024
7 tasks
AzureRestAPISpecReview
added
ARMReview
new-api-version
ReadyForApiTest
<valid label in PR review process>add this label when swagger and service APIs are ready for test
WaitForARMFeedback
<valid label in PR review process> add this label when ARM review is required
BreakingChangeReviewRequired
<valid label in PR review process>add this label when breaking change review is required
NotReadyForARMReview
and removed
WaitForARMFeedback
<valid label in PR review process> add this label when ARM review is required
labels
Jul 29, 2024
cadenmarchese
force-pushed
the
add-20240812preview-2
branch
from
July 30, 2024 20:18
a7c7d98
to
b1e4900
Compare
AzureRestAPISpecReview
added
WaitForARMFeedback
<valid label in PR review process> add this label when ARM review is required
and removed
NotReadyForARMReview
BreakingChangeReviewRequired
<valid label in PR review process>add this label when breaking change review is required
labels
Jul 30, 2024
.../Microsoft.RedHatOpenShift/openshiftclusters/preview/2024-08-12-preview/redhatopenshift.json
Outdated
Show resolved
Hide resolved
.../Microsoft.RedHatOpenShift/openshiftclusters/preview/2024-08-12-preview/redhatopenshift.json
Outdated
Show resolved
Hide resolved
.../Microsoft.RedHatOpenShift/openshiftclusters/preview/2024-08-12-preview/redhatopenshift.json
Outdated
Show resolved
Hide resolved
.../Microsoft.RedHatOpenShift/openshiftclusters/preview/2024-08-12-preview/redhatopenshift.json
Outdated
Show resolved
Hide resolved
.../Microsoft.RedHatOpenShift/openshiftclusters/preview/2024-08-12-preview/redhatopenshift.json
Show resolved
Hide resolved
ms-bogdan-rotaru
added
the
ARMChangesRequested
<valid label in PR review process>add this label when require changes after ARM review
label
Jul 31, 2024
openapi-pipeline-app
bot
removed
the
WaitForARMFeedback
<valid label in PR review process> add this label when ARM review is required
label
Jul 31, 2024
cadenmarchese
added
WaitForARMFeedback
<valid label in PR review process> add this label when ARM review is required
and removed
ARMChangesRequested
<valid label in PR review process>add this label when require changes after ARM review
labels
Aug 13, 2024
gary-x-li
added
the
ARMSignedOff
<valid label in PR review process>add this label when ARM approve updates after review
label
Aug 13, 2024
openapi-pipeline-app
bot
removed
the
WaitForARMFeedback
<valid label in PR review process> add this label when ARM review is required
label
Aug 13, 2024
the required Swagger SpellCheck fails, please fix it first |
razvanbadea-msft
added
the
ARMChangesRequested
<valid label in PR review process>add this label when require changes after ARM review
label
Sep 19, 2024
openapi-pipeline-app
bot
removed
the
WaitForARMFeedback
<valid label in PR review process> add this label when ARM review is required
label
Sep 19, 2024
AzureRestAPISpecReview
added
BreakingChangeReviewRequired
<valid label in PR review process>add this label when breaking change review is required
NotReadyForARMReview
and removed
ARMChangesRequested
<valid label in PR review process>add this label when require changes after ARM review
ReadyForApiTest
<valid label in PR review process>add this label when swagger and service APIs are ready for test
labels
Sep 19, 2024
openapi-pipeline-app
bot
added
the
WaitForARMFeedback
<valid label in PR review process> add this label when ARM review is required
label
Sep 19, 2024
AzureRestAPISpecReview
added
ReadyForApiTest
<valid label in PR review process>add this label when swagger and service APIs are ready for test
and removed
WaitForARMFeedback
<valid label in PR review process> add this label when ARM review is required
labels
Sep 19, 2024
cadenmarchese
force-pushed
the
add-20240812preview-2
branch
from
October 1, 2024 13:41
232cdcd
to
5ccccd6
Compare
AzureRestAPISpecReview
removed
the
ReadyForApiTest
<valid label in PR review process>add this label when swagger and service APIs are ready for test
label
Oct 1, 2024
mikekistler
added
the
BreakingChange-Approved-Benign
Changes are not breaking at the REST API level and have at most minor impact to generated SDKs.
label
Oct 2, 2024
AzureRestAPISpecReview
added
WaitForARMFeedback
<valid label in PR review process> add this label when ARM review is required
BreakingChangeReviewRequired
<valid label in PR review process>add this label when breaking change review is required
NotReadyForARMReview
and removed
NotReadyForARMReview
BreakingChange-Approved-Benign
Changes are not breaking at the REST API level and have at most minor impact to generated SDKs.
BreakingChangeReviewRequired
<valid label in PR review process>add this label when breaking change review is required
WaitForARMFeedback
<valid label in PR review process> add this label when ARM review is required
labels
Oct 8, 2024
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
* ensures reviewers can see changes from new API
commit changes to readme * this file appears required for comparison with Azure types commit v2024-08-12-preview examples add descriptions to all new api fields adjust one of the code comments according to feedback on the Red Hat side add platformworkloadidentityroleset + examples fix relative path to common-types use common-types files directly rather than copying them into the redhatopenshift directory use common-types/v6, use ManagedServiceIdentity type definition fix Swagger SpellCheck remove "format":"uuid" from clientIds, principalIds, tenantIds attempt to fix Swagger LintDiff check convert platformWorkloadIdentities to map
cadenmarchese
force-pushed
the
add-20240812preview-2
branch
2 times, most recently
from
October 11, 2024 20:09
104998f
to
ca2d871
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
ARMReview
BreakingChangeReviewRequired
<valid label in PR review process>add this label when breaking change review is required
new-api-version
NotReadyForARMReview
resource-manager
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 help
section 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 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
suppressions guide to get approval.
Getting help
Purpose of this PR
andDue diligence checklist
.write access
per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Merge
comment. 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.
queued
state, please add a comment with contents/azp run
.This should result in a new comment denoting a
PR validation pipeline
has started and the checks should be updated after few minutes.