[TEP 0075, 0076] More ways of referencing params and results

[ywluogg]

Feature request

There are certain ways of referencing params and results, either as a whole or accessing keys, are implemented and tracked in #4723, but there are other ways that should be considered for accessing params and results.

Thanks for @chuangw6 and @Yongxuanzhang 's summary, the following are supported:

• String Types
  • $(tasks.myTask.results.myStringResult)
  • $(tasks.myTask.results[‘my.String.Result’])
  • $(tasks.myTask.results["my.String.Result"])
• Array Types
  • $(tasks.myTask.results.myArrayResult[*])
  • $(tasks.myTask.results.myArrayResult[i])
• Object Types
  • $(tasks.myTask.results.myObjectResult[*])
  • $(tasks.myTask.results.myObjectResult.key1)

Below are few other ways are listed below that are not supported but should be considerred:

• Array Types
  • $(tasks.myTask.results[‘myArrayResult’][*])
  • $(tasks.myTask.results[“myArrayResult”][*])
  • $(tasks.myTask.results[‘myArrayResult’][i])
  • $(tasks.myTask.results[“myArrayResult”][i])
• Object Types
  • $(tasks.myTask.results[“my.Object.Result”][*])
  • $(tasks.myTask.results[“my.Object.Result”].key1)
  • $(tasks.myTask.results[“my.Object.Result”][“my.key1”])

Use case

Stated above.

[chuangw6]

$(tasks.myTask.results[“my.Object.Result”][*])
$(tasks.myTask.results[“my.Object.Result”].key1)
$(tasks.myTask.results[“my.Object.Result”][“my.key1”])

Object param/result name and its keys shouldn't contain dots. see more details here

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.