-
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
Clarify error message for PipelineRun alpha fields #5045
Conversation
/test pull-tekton-pipeline-build-tests |
/approve |
FYI @austinzhao-go |
This commit updates the error message when a user has specified PipelineRun.spec.taskRunSpecs.stepOverrides without the alpha feature flag enabled to clarify what they need to do to enable the field (and likewise for sidecarOverrides). A similar error message is already used for TaskRun's spec.stepOverrides. It also updates the error message for when a TaskRun's computeResources or PipelineRun.TaskRunSpecs.computeResources are used without the alpha feature flag.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abayer, lbernick 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 |
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
Changes
This commit updates the error message when a user has specified
PipelineRun.spec.taskRunSpecs.stepOverrides without the alpha feature flag
enabled to clarify what they need to do to enable the field (and likewise
for sidecarOverrides). A similar error message is already used for TaskRun's
spec.stepOverrides. It also updates the error message for when a TaskRun's computeResources
or PipelineRun.TaskRunSpecs.computeResources are used without the alpha feature flag.
/kind bug
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
(if there are no user facing changes, use release note "NONE")
Release Notes