When starting a pipeline with a workspace I get Error: Name not found for workspace

[ctron]

Versions and Operating System

• Kubernetes version:

  Output of kubectl version:

  Client Version: v1.28.2
  

Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.25.11+1485cc9
WARNING: version difference between client (1.28) and server (1.25) exceeds the supported minor version skew of +/-1

- Tekton Pipeline version:

**Output of `tkn version` or `kubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'`**

Client version: 0.34.0
Chains version: v0.17.1
Pipeline version: v0.50.3
Triggers version: v0.25.2
Operator version: v0.68.1

- Operating System:

Fedora release 39 (Thirty Nine)

# Expected Behavior

According to the docs, I should be able to specify a workspace like this:

tkn pipeline start --workspace name=my-empty-dir,emptyDir=""

# Actual Behavior

It fails with:

Error: Name not found for workspace

# Steps to Reproduce the Problem

1. Install task and example as described here: https://github.com/ctron/bombastic-tekton-upload#installation (and following section)
2. Run: `tkn pipeline start example -n test -w 'sboms=my-empty-dir,emptyDir=""' -p bombastic-api-url=https://sbom.apps.cluster-8mn59.sandbox909.opentlc.com/api/v1/sbom -p bombastic-issuer-url=https://sso.apps.cluster-8mn59.sandbox909.opentlc.com/realms/chicken -p bombastic-client-id=walker -p bombastic-client-secret=replace-me`
3.

# Additional Info

[vdemeester]

@ctron In the repository, the name of the workspace is input, so the flag should be --workspace name=input,emptyDir={}

[ctron]

I actually just found it out. I am a few minutes late :) … The name is actually sboms, and that's what I used as name. However, name= actually isn't a placeholder, but must literally be name=. I think that should be somewhat clearer.