Conversation
Make sure we always have an up-to-date catalog template. This is done by generating it alongside with `make update-bundle`, which is already enforced by github action checks. Catalog generation makes use of a trick that OLM team told me: using "--alpha-image-ref-template" in opm render allows to generate the catalog in csv-metadata format even though the bundle image doesn't exist yet (it wouldn't work otherwise)
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@jotak: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
PR needs rebase. DetailsInstructions 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. |
1 similar comment
|
PR needs rebase. DetailsInstructions 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. |
2 participants
Make sure we always have an up-to-date catalog template. This is done by generating it alongside with
make update-bundle, which is already enforced by github action checks.Catalog generation makes use of a trick that OLM team told me: using "--alpha-image-ref-template" in opm render allows to generate the catalog in csv-metadata format even though the bundle image doesn't exist yet (it wouldn't work otherwise)