-
Notifications
You must be signed in to change notification settings - Fork 247
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
enforce rfc1123 label compatibility for olm.package.name #1307
enforce rfc1123 label compatibility for olm.package.name #1307
Conversation
Skipping CI for Draft Pull Request. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1307 +/- ##
=========================================
Coverage ? 50.08%
=========================================
Files ? 132
Lines ? 12745
Branches ? 0
=========================================
Hits ? 6383
Misses ? 5307
Partials ? 1055 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Jordan Keister <jordan@nimblewidget.com>
8a21a0a
to
2a030c9
Compare
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.
lgtm - nice one!!! thank you =D
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: grokspawn, perdasilva 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 |
@perdasilva I think this repo needs the leading slash on bot commands, e.g. '/lgtm'. 😞 |
/lgtm |
6bb0a3e
into
operator-framework:master
Thanks @perdasilva! |
Description of the change:
Motivation for the change:
in the interest of facilitating package name uniqueness with FBC catalogs, it's in our best interests to have the key attribute able to satisfy the requirements of
metadata.name
which some storage requires. There is already prior art which prevents compliance with the more stringent RFC1035 (https://dev.operatorhub.io/operator/3scale-community-operator) but there is no currently published operator in public catalogs which fails RFC1123 label compliance inolm.package.name
, so this PR would make that a requirement going forward.Reviewer Checklist
/docs