From 0c3dd6642e6630f6ef4d0cfc0a8849cdabd99155 Mon Sep 17 00:00:00 2001 From: Vincent Demeester Date: Fri, 27 Mar 2020 12:00:45 +0100 Subject: [PATCH] =?UTF-8?q?Add=20ROADMAP.md=20=F0=9F=A4=96?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Vincent Demeester --- README.md | 3 ++- ROADMAP.md | 74 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 76 insertions(+), 1 deletion(-) create mode 100644 ROADMAP.md diff --git a/README.md b/README.md index b406120b5b..8f124cab53 100644 --- a/README.md +++ b/README.md @@ -141,7 +141,7 @@ You should see the following after running kubectl plugin list if tkn is availab /usr/local/bin/kubectl-tkn ``` If the output above is shown, run kubectl-tkn to see the list of available tkn commands to run. - + ### Useful Commands The following commands help you understand and effectively use the Tekton CLI: @@ -168,6 +168,7 @@ We are so excited to have you! - See [CONTRIBUTING.md](CONTRIBUTING.md) for an overview of our processes - See [DEVELOPMENT.md](DEVELOPMENT.md) for how to get started +- See [ROADMAP.md](ROADMAP.md) for the current roadmap - Look at our [good first issues](https://github.com/tektoncd/cli/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) and our diff --git a/ROADMAP.md b/ROADMAP.md new file mode 100644 index 0000000000..995a2b2ac5 --- /dev/null +++ b/ROADMAP.md @@ -0,0 +1,74 @@ +# Roadmap + +## User facing roadmap + +### V1beta1 support and GA + +- Add support for v1beta1 and later on GA +- Warn usage of PipelineResource in v1beta1 (no error but warn that it is not supported aka will work but can be broken in a later release) +- Support for workspace, result, … + +### Improve e2e Testing Coverage for CLI + +- We should do an assessment of what scenarios we have covered for e2e testing and figure out where additional testing is needed + +### Consistency across all CLI resources for list, delete, and describe subcommands + +- We should work to make sure each resource introduced to the CLI always features these three subcommands + +### Filtering for list and delete commands + +- We should provide filtering solutions for all list/delete commands associated with CLI + +### Define and carry out strategy around creation/deletion for the CLI: + +- There are two issues open around this: + - https://github.com/tektoncd/cli/issues/574 + - https://github.com/tektoncd/cli/issues/575 +- There have been requests for a create command for the CLI similar to kubectl create/apply +- We should support one of the above strategies, or we will not support creation/updating like kubectl create/apply -f moving forward +- If we do not support a -f option, we should remove the create -f commands from pipeline/task/resource + +### Catalog integration + +- Related to the OCI experiment + ([#2137](https://github.com/tektoncd/pipeline/issues/2137)) and the + catalog / hub, integrate better with the/a catalog + - Allow searching catalog for a Task, Pipeline, … + - Allow importing a task from the catalog into the cluster + +### Local to cluster build + +- From a user working directory, be able to run a task or pipeline with the content of this working directory + - Use volume (pvc, …) with `workspace` support + - Create / Update volume and start the pipeline +- Related to : Binary (local) input type + [#924](https://github.com/tektoncd/pipeline/issues/924) +- Discovery on creation + - Similar to oc new-app + - Detect stuff, create task, … + +### Source to Pipeline resources + +- be able from the cli auto generate some Pipeline/tasks from a source + code folder detecting what kind of source code it is (i.e: go, java, + python, ruby, rust, project etc...) and automatically apply the + standard from task the catalog. + +## Technical roadmap + +### More Regular Release Process to Test Our Release Process + +- A common problem with releases has been unexpected issues during release attempts: + - https://github.com/tektoncd/cli/pull/673 (0.7.1) + - https://github.com/tektoncd/cli/pull/757 (0.8.0) +- We should have a way of more regularly testing the CLI release process pipeline + +### Re-evaluate plug-in execution model + +- Easier support for experiments + - `tkn install …` could detect and install tekton using different mechanisms (operator on openshift or if it detects OLM, etc…) + - Could be a separate project (hosted by tektoncd/operator or elsewhere) + - Initial catalog / oci integration ? + - Helper to author a catalog task / resource ? (tkn catalog task init … ?) + - Integration with Tekdoc