-
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
param validation - execution status variable #3691
param validation - execution status variable #3691
Conversation
The following is the coverage report on the affected files.
|
Might be worth adding a unit test to check that variables of form |
b5853ab
to
aa6b775
Compare
The following is the coverage report on the affected files.
|
Thanks @sbwsg I have added such unit test. @afrittoli, this PR will needs cherry picking into |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbwsg 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 |
looks good to me |
Adding param validation while accessing execution status along with any other param or extra string. Also, avoiding task results validation as it follows very similar pattern with $(tasks.taskname.results.status) where "status" is a result of some task.
aa6b775
to
6bf700a
Compare
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.
/lgtm
Changes
Adding param validation while accessing execution status along with any other param or extra string. Updated pipelines documenting the limitation.
Also, avoiding task results validation as it follows very similar pattern with
$(tasks.taskname.results.status)
where"status" being the result of some task.
Closes #3681
Closes #3692
/kind misc
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