-
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
[TEP-0075] Validate against using the whole object in task steps #4861
[TEP-0075] Validate against using the whole object in task steps #4861
Conversation
dce66fe
to
07a8117
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
07a8117
to
103bc3f
Compare
103bc3f
to
86720cd
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/assign ywluogg |
86720cd
to
4f10980
Compare
The following is the coverage report on the affected files.
|
/test pull-tekton-pipeline-alpha-integration-tests |
Just wanted to confirm that this PR will still be focused on substituted field is a string, and the substituting param is an object, is it? |
This PR makes sure object param cannot be used as whole in any part of a task step. |
Oh I think I meant to ask - if this PR would be focused on validations of whole object substitutions, when the substituted field is a string? You can close this thread, as I found where you add the validations of substituted param is an array and substituting param is an object. I updated a comment in test cases to help reviewers quickly identify what validations you added more easily. |
4f10980
to
73681ce
Compare
The following is the coverage report on the affected files.
|
/test pull-tekton-pipeline-integration-tests |
/assign @lbernick |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lbernick, ywluogg 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 |
484a061
to
d521656
Compare
The following is the coverage report on the affected files.
|
d521656
to
0070ba8
Compare
The following is the coverage report on the affected files.
|
According to TEP-0075: When providing values for strings, Task and Pipeline authors can access individual attributes of an object param; but they cannot access the object as whole. Also modified `extractVariablesFromString` function a bit to recognize `params.foo.bar` reference that was treated as invalid previously.
0070ba8
to
f576c18
Compare
The following is the coverage report on the affected files.
|
Link this to #4723 |
This needs a release note. |
/lgtm |
/test pull-tekton-pipeline-integration-tests |
/kind feature |
Changes
According to TEP-0075:
When providing values for strings, Task and Pipeline authors can
access individual attributes of an object param; but they cannot access
the object as whole.
This PR makes sure that the object param cannot be used as whole when providing values for strings in task steps.
Also modified
extractVariablesFromString
function a bit to recognizeparams.foo.bar
reference that was treated as invalid previously.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