-
Notifications
You must be signed in to change notification settings - Fork 788
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
Ignore errors if label.Relabel returns ENOSUP #5197
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rhatdan 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 |
@n1hility PTAL |
Awesome! LGTM other than the conflict |
This is a common mistake by users and is ignored in some places but not everywhere. This change will help this to be ignored everwhere. Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
Most of the places where this PR suppresses that error are for files we're creating, where the user doesn't get to tell us whether or not to change the labels on them. The exceptions are the ones in We're pretty inconsistent about where we put files we bind-mount in. An environment secret gets stored under |
I just wanted to be consistent. No reason to not call the same code everwhere. For most of these there will be no change as you point out. but if we spray around label.Relabel and relabel code, there is a decent chance a future contributor could do it wrong. |
I'm fine with the changes, but will let you and @nalind thumb-wrestle out the details. |
/lgtm |
This is a common mistake by users and is ignored in some places but not everywhere. This change will help this to be ignored everwhere.
What type of PR is this?
What this PR does / why we need it:
How to verify it
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?
[NO NEW TESTS NEEDED]