-
Notifications
You must be signed in to change notification settings - Fork 11
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
Build file-based catalog #123
Conversation
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: clobrano 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 |
It's ok now |
1a7990e
to
13850f2
Compare
/test 4.15-openshift-e2e |
1 similar comment
/test 4.15-openshift-e2e |
|
13850f2
to
ef36b28
Compare
ef36b28
to
36f9b20
Compare
/test 4.15-openshift-e2e |
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 very nice, left some nits
.PHONY: catalog-build | ||
catalog-build: opm ## Build a file-based catalog image. | ||
# Remove the catalog directory and Dockerfile if they exist | ||
-rm -r ${CATALOG_DIR} ${CATALOG_DOCKERFILE} |
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.
If you first remove the directory then why afterward you would need to delete a file that was in that directory?
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.
The file isn't inside the directory, it's prefixed with the directory's name
e.g.
catalog_dir
and catalog_dir.Dockerfile
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.
Why? Is there a reason for that?
It looks better to have catalog.Dockerfile
instead of catalog_dir.Dockerfile
similar to the naming format of the bundle Dockerfile that we currently have bundle.Dockerfile
WDYT?
BTW it would be nicer to have this file under the CATALOG_DIR directory if we want to have it as a temporary file.
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.
Why? Is there a reason for that?
opm generate dockerfile
works this way [1] 🤷
It looks better to have catalog.Dockerfile
I can change the name of the <catalog_dir>
no problem (of course we don't keep this file, but I don't have strong preferences)
[1] https://docs.openshift.com/container-platform/4.14/operators/admin/olm-managing-custom-catalogs.html
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.
CATALOG_DIR := catalog
It is fine, and it would result in catalog.Dockerfile
according to steps 1b and 1c in OCP docs.
36f9b20
to
66cfe96
Compare
Signed-off-by: Carlo Lobrano <c.lobrano@gmail.com>
66cfe96
to
1ba63fd
Compare
/lgtm |
It doesn't |
@clobrano: The following test failed, say
Full PR test history. Your PR dashboard. Instructions 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/test-infra repository. I understand the commands that are listed here. |
Drop the deprecated db-based catalog in favor of the new file-based catalog.
https://issues.redhat.com/browse/ECOPROJECT-1008