search

openshift / file-integrity-operator

Operator providing OpenShift cluster node file integrity checking
Apache License 2.0
31 stars 27 forks source link

CMP-2175: Implement support for replaces attribute in CSV #525

Open rhmdnd opened 6 months ago

rhmdnd commented 6 months ago

Doing this makes it so that OLM can build dependency graphs between operator versions, which make it easier for users perform installs on disconnected environments and upgrades.

openshift-ci-robot commented 6 months ago

@rhmdnd: This pull request references CMP-2175 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 story to target the "4.16.0" version, but no target version was set.

In response to [this](https://github.com/openshift/file-integrity-operator/pull/525): >Doing this makes it so that OLM can build dependency graphs between >operator versions, which make it easier for users perform installs on >disconnected environments and upgrades. > Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Ffile-integrity-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
openshift-ci[bot] commented 6 months ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rhmdnd

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: - ~~[OWNERS](https://github.com/openshift/file-integrity-operator/blob/master/OWNERS)~~ [rhmdnd] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
openshift-ci[bot] commented 6 months ago

@rhmdnd: The following tests 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/e2e-bundle-aws-upgrade 16478aa061cdca3ce4efd6414bc48d1389986c9f link true /test e2e-bundle-aws-upgrade
ci/prow/e2e-aws 16478aa061cdca3ce4efd6414bc48d1389986c9f link true /test e2e-aws
ci/prow/images 16478aa061cdca3ce4efd6414bc48d1389986c9f link true /test images
ci/prow/ci-index-file-integrity-operator-bundle 16478aa061cdca3ce4efd6414bc48d1389986c9f link true /test ci-index-file-integrity-operator-bundle
ci/prow/e2e-bundle-aws 16478aa061cdca3ce4efd6414bc48d1389986c9f link true /test e2e-bundle-aws

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
Vincent056 commented 3 months ago

@rhmdnd could you rebase this PR, thanks!

openshift-bot commented 3 weeks ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale