Closed lstocchi closed 3 years ago
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.
/remove-lifecycle stale
resolved in https://github.com/tektoncd/cli/pull/1377 /close
@vinamra28: Closing this issue.
Versions and Operating System
Kubernetes version:
Output of
kubectl version
:Tekton Pipeline version:
Output of
tkn version
orkubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'
Expected Behavior
Being able to start a task/pipeline that has an optional workspace without specifying the workspace. If the task has 2 params and 1 workspace (optional) as inputs i should be able to start the task by only passing the two params values
Actual Behavior
Even if my task has a workspace which is optional, the cli keeps asking me to add it when i try to start the task
Steps to Reproduce the Problem
Additional Info
I faced this error while working on the IJ Tekton plugin. Let me know if there is a way to bypass it. Do we need to feed the cli somehow?