OCPSTRAT-2713: Bump ignition from 3.2 to 3.6#10392
OCPSTRAT-2713: Bump ignition from 3.2 to 3.6#10392fangge1212 wants to merge 1 commit intoopenshift:mainfrom
Conversation
|
Important Review skippedAuto reviews are limited based on label configuration. 🚫 Review skipped — only excluded labels are configured. (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
WalkthroughUpgrades numerous Go module dependencies in go.mod and replaces Ignition imports from github.com/coreos/ignition/v2/config/v3_2 to v3_6 across the codebase, updating type package references (including exported struct fields that reference igntypes.Config). Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
e046b7a to
b7c3925
Compare
|
@fangge1212: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
b7c3925 to
d078874
Compare
The latest ignition contains the API addtion to deploy confidential clusters. Signed-off-by: Alice Frosi <afrosi@redhat.com> Signed-off-by: Fangge Jin <fjin@redhat.com>
d078874 to
0889fd9
Compare
|
@fangge1212: This pull request references OCPSTRAT-2713 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the feature to target either version "4.22." or "openshift-4.22.", but it targets "openshift-5.0" instead. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
Might want to run these tests. I'm thinking moving the draft state to open will trigger it. Ready if you are. |
The latest ignition contains the API addtion to deploy confidential clusters.