-
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
fix ValidateStepResultsVariables to validate stepResults only #8264
base: main
Are you sure you want to change the base?
Conversation
a7cd2bb
to
8e0fa48
Compare
/kind bug |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
8e0fa48
to
0c6cd04
Compare
0c6cd04
to
18dee1a
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
18dee1a
to
7c5e691
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
e078cdd
to
98e4c6f
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
98e4c6f
to
f1fc5c5
Compare
The following is the coverage report on the affected files.
|
/test pull-tekton-pipeline-beta-integration-tests |
1 similar comment
/test pull-tekton-pipeline-beta-integration-tests |
/test pull-tekton-pipeline-go-coverage-df |
@afrittoli: The specified target(s) for
The following commands are available to trigger optional jobs:
Use In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
The following is the coverage report on the affected files.
|
@jkhelil It would be great if this is covered as part of e2e if possible to add |
f1fc5c5
to
5a87c4a
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester 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 |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
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 for catching and fixing this issue.
I think there is an issue with the current fix though - see my comments inline.
/hold
}, { | ||
name: "step script refers to nonexistent result", | ||
fields: fields{ | ||
Image: "my-image", | ||
Script: ` | ||
#!/usr/bin/env bash | ||
date | tee $(results.non-exist.path)`, | ||
Results: []v1.StepResult{{Name: "a-result"}}, | ||
}, | ||
expectedError: apis.FieldError{ | ||
Message: `non-existent variable in "\n\t\t\t#!/usr/bin/env bash\n\t\t\tdate | tee $(results.non-exist.path)"`, | ||
Paths: []string{"script"}, | ||
}, |
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.
The fact that you have to remove this test here highlights another problem in the current codebase.
You want to fix an issue in how we validate an inline step in a Task
definition, and this has a side effect on the validation of a StepAction
, which should not happen.
In the task-stepaction-results.yaml
example that you provided, an inline step references to a Task
result, which is valid and should work, and doesn't work today, which is the problem that needs to be fixed.
This stems from the fact that ValidateStepResultsVariables
does not have enough context to validate Task
level references, which are validated instead by ValidateTaskResultsVariables
as you mentioned.
The change you proposed, however, modifies code used for validation of StepActions
, which is not ok, as exemplified by the test you removed, which should continue to pass. The author of a StepAction
has no knowledge about the Tasks
that may use it, and should not reference any variable outside of the known context.
A correct fix for the issue should include, on top of the fix already done, a change in the stepaction_validation
code, which, instead of using ValidateStepResultsVariables
from the task validation, should define its own ValidateStepActionResultsVariables
, which should look like what ValidateStepResultsVariables
looks today.
Unit tests should not be removed and we should make sure we have a unit tests that validates ValidateTaskResultsVariables
(which we most likely already have).
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.
@afrittoli I think you're right to add ValidateStepActionResultsVariables that validates step results only because it has only the step results context and hence i removed the snippet of tests there (we dont have the task result context when using stepAction.Validate)
I am also fixing ValidateStepResultsVariables to add task results in the function args so we can validate the step script against both step and task result because we have them in context as this method is now only called in task validation context
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.
@afrittoli Can you have a look to my comment pleae
5a87c4a
to
49fb44c
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
…nd fix ValidateStepResultsVariables to include task results validation
49fb44c
to
1a958c3
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
Changes
fixes #8255
There is a mixture of validating step result and task result in both ValidateStepResultsVariables
ValidateStepResultsVariables should use step results set of name to only validate StepResults. TaskResults are validated via the function ValidateTaskResultsVariables
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes