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

🌱 add copy-content to goreleaser and release artifacts #3277

Merged

Conversation

perdasilva
Copy link
Collaborator

Description of the change:
I've noticed that copy-content is missing from the release artifacts. This PR adds it to goreleaser and the released images

Motivation for the change:
copy-content is used for a particular mode of CatalogSource that uses the registry image only for its content (not using its opm server)

Architectural changes:

Testing remarks:

Reviewer Checklist

  • Implementation matches the proposed design, or proposal is updated to match implementation
  • Sufficient unit test coverage
  • Sufficient end-to-end test coverage
  • Bug fixes are accompanied by regression test(s)
  • e2e tests and flake fixes are accompanied evidence of flake testing, e.g. executing the test 100(0) times
  • tech debt/todo is accompanied by issue link(s) in comments in the surrounding code
  • Tests are comprehensible, e.g. Ginkgo DSL is being used appropriately
  • Docs updated or added to /doc
  • Commit messages sensible and descriptive
  • Tests marked as [FLAKE] are truly flaky and have an issue
  • Code is properly formatted

@openshift-ci openshift-ci bot requested review from awgreene and stevekuznetsov May 25, 2024 13:58
@perdasilva perdasilva enabled auto-merge May 27, 2024 07:59
@@ -7,6 +7,7 @@ RUN ["/busybox/ln", "-s", "/busybox/cp", "/bin/cp"]
COPY olm /bin/olm
COPY catalog /bin/catalog
COPY package-server /bin/package-server
COPY copy-content /bin/copy-content
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do I understand correctly - this is what ends up in the image we push to quay on release?

Copy link
Collaborator Author

@perdasilva perdasilva May 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's right. We've been shipping without it =S
Downstream has been fine because we don't use this makefile or image for building/releasing

@perdasilva perdasilva added this pull request to the merge queue May 27, 2024
Merged via the queue into operator-framework:master with commit 2334c05 May 27, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants