Skip to content
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

OADP-5245: Operator SDK update guidelines #1613

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

mateusoliveira43
Copy link
Contributor

Why the changes were made

Fix #1540

Changes were made following documentation about how to upgrade Operator SDK version, from 1.23.0 to 1.34.2.

Changes are necessary to allow creation of webhooks for NAC CRDs.

How to test the changes made

Run commands to confirm that after the changes they still work. For example

make help
make generate
make bundle
make lint
make test
make deploy-olm
make test-e2e

Read documentation about how to upgrade Operator SDK version and check if it is clear.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 5, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 5, 2025

@mateusoliveira43: This pull request references OADP-5245 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 task to target the "4.19.0" version, but no target version was set.

In response to this:

Why the changes were made

Fix #1540

Changes were made following documentation about how to upgrade Operator SDK version, from 1.23.0 to 1.34.2.

Changes are necessary to allow creation of webhooks for NAC CRDs.

How to test the changes made

Run commands to confirm that after the changes they still work. For example

make help
make generate
make bundle
make lint
make test
make deploy-olm
make test-e2e

Read documentation about how to upgrade Operator SDK version and check if it is clear.

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.

@openshift-ci openshift-ci bot requested review from mrnold and sseago January 5, 2025 01:47
Copy link

openshift-ci bot commented Jan 5, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mateusoliveira43

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 5, 2025
@mateusoliveira43

This comment was marked as resolved.

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 5, 2025
@mateusoliveira43

This comment was marked as resolved.

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 5, 2025
Copy link

openshift-ci bot commented Jan 5, 2025

@mateusoliveira43: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/4.15-e2e-test-aws d1f6ee8 link true /test 4.15-e2e-test-aws

Full PR test history. Your PR dashboard.

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.

@@ -1,23 +1,26 @@
/*
Copyright 2021.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you know where 2021 is coming from?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we update that here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

since it is not necessary for it to work, no. Can be a separate PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Create operator-sdk update guidelines
3 participants