-
Notifications
You must be signed in to change notification settings - Fork 252
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
Adding ability to deprecate bundles #397
Adding ability to deprecate bundles #397
Conversation
7ac5a86
to
5ba1584
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- We need tests
- Add an example string for the command
- We need to enhance add to undo the deprecation (add back deprecated bundle mark it's replaced bundle as deprecated)
Is that part necessary? I keep hearing about these requests from the pipelines that they need to have "undo" commands. But can't they just... point to a version of the index that didn't remove it yet? |
In the enhancement we punted on that command https://github.com/operator-framework/enhancements/blob/master/enhancements/deprecated-bundles.md#story-2 in favor of using images as @kevinrizza suggested |
3349788
to
f3cd926
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me
f3cd926
to
0f106ea
Compare
0f106ea
to
d888951
Compare
/retest |
1 similar comment
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few open questions. Nice work @gallettilance
d888951
to
2c8e28e
Compare
/lgtm |
/retest |
1 similar comment
/retest |
/retest |
/lgtm |
}, | ||
}, | ||
}, | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is looking pretty good, but doesn't quite convince me that there are no bugs - at the very least I think this should verify the full end state of the graph, not just the bundles/packages/channels.
I also want to make sure that this covers:
- bundle is in two channels
- bundle is in two packages
- bundle is skipped by another bundle
- bundle has children that are skipped that get removed
(it might already cover these implicitly, just need to check)
/lgtm so far. There are still a new comments from Evan & Alex need to be address and then this PR should be good to go. |
2c8e28e
to
65b728e
Compare
Adding support marking bundles as deprecated and truncating the update graph of a given package. Deprecated versions will not be installable. Deprecating a bundle can result in the removal of channels but this is not permitted for the default channel. Bundles that are not in the index will be ignored during deprecation.
65b728e
to
dcc7e50
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gallettilance, kevinrizza, shawn-hurley 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 |
/retest |
/lgtm |
/test e2e-aws |
/retest Please review the full test history for this PR and help us cut down flakes. |
@gallettilance I realize this was merged quite some time ago, but why wasn't the |
Adding support marking versions as deprecated and truncating the update
graph of a given package. Deprecated versions will not be installable.
If a deprecated version is installed prior to upgrade appropriate alerts
will be fired on cluster.
Description of the change:
Described in this enhancement
Motivation for the change:
Reviewer Checklist
/docs