tektoncd / tektoncd/cli

Show Param Values Added by Pipelines Controller for PipelineRun/TaskRun Describe

Open
#1,072 15 comments 1 reaction 1 assignee View on GitHub

@GwonsooLee is already working on this.

Since Aug 18, 2020.

help wanted kind/feature
Dominant language
Go
Stars
461
Forks
277
Avg merge
16h 48m
Merged PRs (30d)
95

Description

Feature request

The ability to see param names/values added by the pipelines controller as opposed to by the user when using tkn pipelinerun desc or tkn taskrun desc. The pipelines controller will add param values in the case of default values for params that are part of a Task or Pipeline.

If no value is declared for a param for a PipelineRun/TaskRun and the associated Task or Pipeline has default values for params, the default values are used and added to the PipelineRun/TaskRun status.

Currently, describe commands for PipelineRun/TaskRun only show param values that are part of the spec of a PipelineRun/TaskRun, but they should also show default values added by the controller.

See more in #1036 for discussion of this.

Use case

Seeing all param values that are part of a PipelineRun/TaskRun to aid with development/debugging PipelineRuns/TaskRuns.

UI Example
Name:        sleep1s-run-9sjsq
Namespace:   default
Task Ref:    sleep1s
Timeout:     1h0m0s
Labels:
 app.kubernetes.io/managed-by=tekton-pipelines
 tekton.dev/task=sleep1s

🌡️  Status

STARTED         DURATION     STATUS
2 minutes ago   13 seconds   Succeeded

📨 Input Resources

 No input resources

📡 Output Resources

 No output resources

⚓ Params
 NAME             VALUE
 ∙ defaultParam   defaultValue


🦶 Steps

 NAME      STATUS
 ∙ sleep   Completed
 ∙ echo2   Completed
 ∙ echo3   Completed
 ∙ echo4   Completed
 ∙ echo5   Completed

🚗 Sidecars

No sidecars

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.