-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[cherry-pick] Fix TaskRunSpec overrides when empty 🗜 #3441
[cherry-pick] Fix TaskRunSpec overrides when empty 🗜 #3441
Conversation
/lgtm Looking Good! 🤙🏽 |
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: afrittoli 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 |
ah, I was too naive 😅 |
In case of TaskRunSpec being present on a PipelineRun, we override the PipelineTask PodTemplate and ServiceAccount blindly, even if those values are empty (empty string, nil point) This fixes this behavior by overriding PodTemplate and/or ServiceAccountName only when they are not empty values. Signed-off-by: Vincent Demeester <[email protected]> (cherry picked from commit 695d117) Signed-off-by: Vincent Demeester <[email protected]>
ca8b286
to
fa7aa64
Compare
/retest |
/lgtm Looking Good! 🤙🏽 |
Changes
In case of TaskRunSpec being present on a PipelineRun, we override the
PipelineTask PodTemplate and ServiceAccount blindly, even if those
values are empty (empty string, nil point)
This fixes this behavior by overriding PodTemplate and/or
ServiceAccountName only when they are not empty values.
Signed-off-by: Vincent Demeester [email protected]
(cherry picked from commit 695d117)
Signed-off-by: Vincent Demeester [email protected]
/kind bug
/cc @afrittoli @chmouel @sbwsg @pritidesai
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Double check this list of stuff that's easy to miss:
cmd
dir, please updatethe release Task to build and release this image.
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes