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

Update opm package, channel, bundle name validation #1437

Open
everettraven opened this issue Sep 3, 2024 · 0 comments
Open

Update opm package, channel, bundle name validation #1437

everettraven opened this issue Sep 3, 2024 · 0 comments

Comments

@everettraven
Copy link
Contributor

everettraven commented Sep 3, 2024

Package

We should move to DNS 1123 Subdomain in opm validate (ideally moved into the model.go validations) to align with ClusterExtension validation which discovered a few other package names that are invalid with our current validation.

Channel

We should add (or move to) DNS 1123 Subdomain in opm validate (ideally moved into the model.go validations) to align with ClusterExtension validation which discovered a few other channel names that are invalid with our current validation.

Bundle

TBD - need to find a spec or pattern that matches all currently known bundle names. Given most bundle names are <packageName>.v<version>, we likely can use DNS 1123 subdomain validation for bundle names here as well.

https://gist.github.com/everettraven/4691c8cc6181f28b129f46cceeb602b5

@joelanford joelanford changed the title Channel names should have stricter validation Update opm package, channel, bundle validation Nov 6, 2024
@joelanford joelanford changed the title Update opm package, channel, bundle validation Update opm package, channel, bundle name validation Nov 6, 2024
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

1 participant