feat : add structured JSON input for start commands

[vikashkumar2020]

Changes

Add a --json flag to tkn pipeline start and tkn task start so users can provide a PipelineRunSpec or TaskRunSpec as JSON.

The flag supports:

• inline JSON
• to read JSON from stdin
• @path to read JSON from a file

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Includes tests (if functionality changed/added)
• Run the code checkers with make check
• Regenerate the manpages, docs and go formatting with make generated
• Commit messages follow commit message best practices

See the contribution guide
for more details.

Release Notes

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: vikashkumar2020 / name: Vikash Kumar (00f2d01, 80ca850)

[chmouel]

is it possible to add json output too ?

[vikashkumar2020]

is it possible to add json output too ?

pipeline :

apiVersion: tekton.dev/v1
kind: Pipeline
metadata:
  name: demo-pipeline
spec:
  params:
    - name: foo
      type: string
      default: default-value
  tasks:
    - name: echo
      taskSpec:
        params:
          - name: foo
            type: string
        steps:
          - name: echo
            image: bash:latest
            script: |
              echo "$(params.foo)"
      params:
        - name: foo
          value: "$(params.foo)"

cmd

./tkn pipeline start demo-pipeline --json '{"params":[{"name":"foo","value":"hello-json"}]}'

output

{
	"kind": "PipelineRun",
	"apiVersion": "tekton.dev/v1",
	"metadata": {
		"generateName": "demo-pipeline-run-",
		"namespace": "default"
	},
	"spec": {
		"pipelineRef": {
			"name": "demo-pipeline"
		},
		"params": [
			{
				"name": "foo",
				"value": "hello-json"
			}
		],
		"taskRunTemplate": {}
	},
	"status": {}
}

[Copilot]

Pull request overview

Adds a new --json flag to tkn task start and tkn pipeline start so users can provide structured JSON to populate parts of the generated TaskRun/PipelineRun spec (supporting inline JSON, stdin via -, and file via @path). This fits into the CLI’s start-command workflow by augmenting the existing flag/interactive inputs and updating the generated docs accordingly.

Changes:

• Introduces --json flag handling in task/pipeline start commands (inline / stdin / @file).
• Merges selected JSON *RunSpec fields into the generated TaskRun / PipelineRun objects and skips interactive prompting when --json is set.
• Adds unit/integration-style tests and updates generated markdown + manpage docs.

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
pkg/cmd/task/start.go	Adds --json flag, JSON resolution, and merges JSON spec fields into TaskRun.
pkg/cmd/task/start_test.go	Adds coverage for --json (inline/malformed/missing file) plus readJSONSpec tests.
pkg/cmd/pipeline/start.go	Adds --json flag, JSON resolution, and merges JSON spec fields into PipelineRun.
pkg/cmd/pipeline/start_test.go	Adds coverage for --json (inline/malformed/missing file) plus readJSONSpec tests.
docs/man/man1/tkn-task-start.1	Documents new --json flag for task start.
docs/man/man1/tkn-pipeline-start.1	Documents new --json flag for pipeline start.
docs/cmd/tkn_task_start.md	Updates generated markdown docs with --json.
docs/cmd/tkn_pipeline_start.md	Updates generated markdown docs with --json.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[vikashkumar2020]

updated

[tekton-robot]

[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

Details

Needs approval from an approver in each of these files:

• OWNERS [vdemeester]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[chmouel]

actually i was wrong about --json output we already have -o json, is there differences between the two? maybe this is just an alias