Task Result path should be available as a variable #1977
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
maybe-next-milestone
For consideration when planning the next milestone
Expected Behavior
The path for a task result should be available as a variable that can be interpolated into scripts. Example YAML we'd like to support:
In the above example we'd like
$(results.current-date-unix-timestamp.path)
to resolve to/tekton/results/current-date-unix-timestamp
.Actual Behavior
At the moment the user has to hard-code the task result path into their Task's script. In other words, if a user wants their Step Container to emit a task result then they need to physically write out
/tekton/results/result-name
in their code.Additional Info
Suggested by @afrittoli here.
The text was updated successfully, but these errors were encountered: