-
Notifications
You must be signed in to change notification settings - Fork 502
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
Allow string slices as krel obs
arguments
#3267
Conversation
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
This fixes the usage of packages and architectures as mentioned in kubernetes#3224 by using a custom separator. We cannot use the GCB separator substitution (see `gcloud topic escaping`) because GCB complains that a 'build tag must match format "^[\\w][\\w.-]{0,127}$"'. Signed-off-by: Sascha Grunert <[email protected]>
dae6097
to
8770eb7
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.
Thank you for taking care of this!
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, saschagrunert, xmudrii 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 |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This fixes the usage of packages and architectures as mentioned in #3224 by using a custom separator.
We cannot use the GCB separator substitution (see
gcloud topic escaping
) because GCB complains that a 'build tag must match format "^[\w][\w.-]{0,127}$"'.Which issue(s) this PR fixes:
Fixes #3224
Special notes for your reviewer:
Tested via:
https://console.cloud.google.com/cloud-build/builds/8480b7dd-2b36-44c2-87c1-f2af0caeaac6?project=648026197307
Does this PR introduce a user-facing change?