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

Introduce IBM Container Registry delete #1043

Merged
merged 1 commit into from
Apr 21, 2022
Merged

Conversation

HeavyWombat
Copy link
Contributor

@HeavyWombat HeavyWombat commented Apr 21, 2022

Changes

The IBM Container Registry (ICR) does not support the standard registry delete
call, similar to DockerHub. Instead, a custom API call needs to be used.

Add ICR login and ICR delete functions analog to the DockerHub functions.

Use the same error message for both custom delete functions.

Fix missing --secret-path in pull and unpack from private registry test case.

In order to (unit) test this locally, set the following environment variables before running Ginkgo:

$ export TEST_BUNDLE_REGISTRY_TARGET=us.icr.io/somenamespace  # or docker.io/somenamespace
$ export TEST_BUNDLE_DOCKERCONFIGFILE=$HOME/.docker/config.json
$ ginkgo run cmd/bundle

Submitter Checklist

  • Includes tests if functionality changed/was added
  • Includes docs if changes are user-facing
  • Set a kind label on this PR
  • Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.

Release Notes

Fixed delete issue for bundle image prune feature when using the IBM Container Registry for the source image

@HeavyWombat HeavyWombat added kind/bug Categorizes issue or PR as related to a bug. kind/feature Categorizes issue or PR as related to a new feature. labels Apr 21, 2022
@openshift-ci openshift-ci bot added the release-note Label for when a PR has specified a release note label Apr 21, 2022
@openshift-ci openshift-ci bot requested review from imjasonh and otaviof April 21, 2022 11:05
cmd/bundle/main.go Outdated Show resolved Hide resolved
cmd/bundle/main.go Show resolved Hide resolved
@SaschaSchwarze0 SaschaSchwarze0 changed the title Introduce IBM Containter Registry delete Introduce IBM Container Registry delete Apr 21, 2022
The IBM Container Registry (ICR) does not support the standard registry delete
call, similar to DockerHub. Instead, a custom API call needs to be used.

Add ICR login and ICR delete functions analog to the DockerHub functions.

Use the same error message for both custom delete functions.

Fix missing `--secret-path` in pull and unpack from private registry test case.
Copy link
Member

@SaschaSchwarze0 SaschaSchwarze0 left a comment

Choose a reason for hiding this comment

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

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 21, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 21, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SaschaSchwarze0

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 21, 2022
@openshift-merge-robot openshift-merge-robot merged commit 1a2b6f6 into main Apr 21, 2022
@HeavyWombat HeavyWombat deleted the fix/icr-delete branch April 22, 2022 07:02
@SaschaSchwarze0 SaschaSchwarze0 added this to the release-v0.10.0 milestone May 23, 2022
@SaschaSchwarze0 SaschaSchwarze0 removed the kind/feature Categorizes issue or PR as related to a new feature. label Jun 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. release-note Label for when a PR has specified a release note
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants