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

How to modify an already merged operator? #2092

Closed
benjaminjb opened this issue Dec 22, 2022 · 2 comments
Closed

How to modify an already merged operator? #2092

benjaminjb opened this issue Dec 22, 2022 · 2 comments

Comments

@benjaminjb
Copy link
Contributor

benjaminjb commented Dec 22, 2022

What is the protocol for updating an already merged operator bundle?

After we merged this PR, we discovered a problem with the OperatorHub installer for OCP v4.8.

(For the curious, it's a problem that this PR addresses: operator-framework/operator-registry@8720e3d -- our bundle is too big and v4.8 has no gzip option.)

Now we want to update all our 5.3.0 bundles so that the minimum OCP is 4.9. How do we go about updating this already merged operator bundle? Is there a set protocol that we can do or do we require different permissions to, say, delete the operator 5.3.0 bundle and re-add it with the appropriate changes?

(Duplicate of redhat-openshift-ecosystem/certified-operators#1702 since this affects both repos, in case there's a solution that covers both.)

@benjaminjb
Copy link
Contributor Author

Working with someone over on certified-operators on this currently; this might be too costly to fix at the moment, but leaving open to think about.

@benjaminjb
Copy link
Contributor Author

Closing this as answered elsewhere; for now we are leaving this as is.

@benjaminjb benjaminjb closed this as not planned Won't fix, can't repro, duplicate, stale Jan 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant