Implementation details for results emitting in TEP-0076 #4805
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
Feature request
This is part of #4723 area 2.
Right now the results are written to /tekton/results/resultname file, and the content will be read and stored as string in
v1beta1.PipelineResourceResult
's value, later it will be written to termination message.To support array and later object type for results. I suggest we change the type of
v1beta1.PipelineResourceResult.Value
fromstring
tov1beta1.ArrayOrString
, and when we read the bytes from results file we can check and unmarshal them intov1beta1.ArrayOrString
.The pro of this is that the json marshal and unmarshal will be easier when handling results data.
This can be done here
pipeline/pkg/entrypoint/entrypointer.go
Lines 197 to 212 in 68f2a66
For later json schema validation, as suggested by @ywluogg, we can validate later here, since we can easily get the taskspec.
pipeline/pkg/pod/status.go
Lines 224 to 232 in 68f2a66
Use case
The text was updated successfully, but these errors were encountered: