-
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-0142: Passing StepResults between Steps #7458
TEP-0142: Passing StepResults between Steps #7458
Conversation
/hold wait for some initial feedback on the approach before adding tests. |
0df8c95
to
d217d36
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
d217d36
to
b28e93a
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.
|
/assign @wlynch @vdemeester @afrittoli This implementation is based on our discussion in the Slack thread. Once we agree on this approach, I can wrap it up with a bit of cleanup, docs and tests. |
b28e93a
to
2168a53
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
2168a53
to
eee2969
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
eee2969
to
8bdd145
Compare
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.
- Do we validate that
steps.<stepName>.results.<resultName>
can only be used in those (command
,args
,scripts
andenv
) ?
Great catch. I don't think we validate that. We allow it in any field. The substitution would not be made there. Though I think that would result in silent errors. I can add the validation that it can only be used in the four fields. Thanks! |
a00a75a
to
3dbfb5c
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
Done! PTAL. |
The following is the coverage report on the affected files.
|
3dbfb5c
to
9fb3e93
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
ping @wlynch @vdemeester whenever you have a chance. This is ready for review. I have removed the ability to perform step-result substitutions directly in steps. Users need to now go to it via env. |
[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 |
This PR enables passing step results between steps. The replacements of stepresults needs to happen in the entrypointer.
9fb3e93
to
32a2db4
Compare
The following is the coverage report on the affected files.
|
/lgtm |
The following is the coverage report on the affected files.
|
This PR adds the capability for passing
Step Results
betweenSteps
using$(steps.stepName.results.resultName...)
like syntax which is one of the known limitations of step actions. It fixes Issue #7420.Changes
The replacements for
$(steps.stepName.results.resultName...)
need to happen in the entrypointer:env
: update os.Environcommand + args
: update e.Commandscript
: Not AllowedSubmitter 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
/kind feature