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

Test for naming conflicts in the opensuse/ namespace #493

Open
dirkmueller opened this issue Jun 4, 2024 · 1 comment
Open

Test for naming conflicts in the opensuse/ namespace #493

dirkmueller opened this issue Jun 4, 2024 · 1 comment

Comments

@dirkmueller
Copy link
Member

There could be a container submitted into openSUSE Tumbleweed that publishes under registry.opensuse.org/opensuse/* under the same name like BCI-dockerfile-generated containers. we might want to have an automated test somewhere that identifies those clashes and highlights/notifies the team on the conflict so that it can be manually resolved somehow.

As discussed in BCI-sync 06-04

@Vogtinator
Copy link
Member

It's not that easy:

  1. It's explicitly supported that tags move between containers over time (e.g. unstable -> stable -> oldstable)
  2. Some tags are provided by multiple containers (e.g. python-3.10-image, python-3.11-image and python-3.12-image all provide opensuse/bci/python:3)

1 means we can't just query the registry for whatever is published, but need to ask OBS what's currently in openSUSE:Factory. I'm not aware of an API that returns tags based on project/repo/arch and fetching+parsing .containerinfo of all binaries does not scale.

2 means there will be false positives and it can't effectively be automated.

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

No branches or pull requests

2 participants