NETOBSERV-727 Update bundle process #205
Conversation
jotak
force-pushed
the
update-bundle-process
branch
3 times, most recently
from
3fc8b62
to
7f2b006
Compare
| operators.operatorframework.io.metrics.builder: operator-sdk-v1.25.2 | ||
| operators.operatorframework.io.bundle.channels.v1: v0.2.x | ||
| operators.operatorframework.io.bundle.channel.default.v1: v0.2.x | ||
| operators.operatorframework.io.metrics.builder: operator-sdk-v1.22.2 |
There was a problem hiding this comment.
Shall we use latest operator-sdk by default or stick to a given version?
There was a problem hiding this comment.
I think we don't need to enforce a specific version, as long as the produced bundle stays the same, minus that particular line ?
In the new github action to verify the bundle, this line is ignored (as well as the "createdAt" line in CSV)
There was a problem hiding this comment.
given that, if someone uses a too old operator-sdk that produces different bundle, the github action will throw a failure, so that will force us to upgrade operator-sdk when necessary
The bundle process needs to work both for upstream and downstream Every time someone changes something that would alter the bundle (e.g. CSV description), they should run "make bundle" (with no options) It will generate the CSV with injected upstream description. The downstream description will be updated too, but not injected: this step will be done later on, in midstream.
jotak
force-pushed
the
update-bundle-process
branch
from
7f2b006
to
ff287bb
Compare
|
New changes are detected. LGTM label has been removed. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jotak 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 |
Requires #200
The bundle process needs to work both for upstream and downstream
Every time someone changes something that would alter the bundle (e.g.
CSV description), they should run "make bundle" (with no options)
It will generate the CSV with injected upstream description.
The downstream description will be updated too, but not injected: this
step will be done later on, in midstream.