Open developer-guy opened 2 years ago
@developer-guy that's an idea that has been there for a while (https://github.com/tektoncd/cli/issues/61) and our current take would be to install it through the operator most likely.
That said, given that we have a "plugin" support, the implementation of such a command could be experimented outside of the tektoncd/cli scope to start with. In any case, that would be indeed a great feature to have.
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.
/lifecycle frozen
Feature request
Why don't we add support for deploying Tekton Pipelines, Chains, Dashboard via tkn CLI? IMHO, it'd be great if I could type:
Use case
We use plain YAML manifests to deploy these applications. It'd be great to add this installation logic into the tkn CLI so that the tkn CLI would become an only needed application from the user's perspective. IMHO, who has tkn CLI, should do anything without requiring the knowledge of installations these tools.
UI Example
Like istioctl did, we might do the same for tkn CLI. There are two things that we have to consider.
How do users set override values for the installation of each application?
Which method should we use under the hood?