We are using the old cli 0.7.1

When #14 will be merged users will be able to check configurations they want but they will not be able to edit them. We should add this feature.

Currently the form to start a task allows user to set input/output resources. We should add support to enable user override paths for a resource.

Cli currently doesn't support this -> tektoncd/cli#807

Users should be able to run a task by using the extension

Update description as it refers to OpenShift Connector

We should limit the number of pipelineruns/taskruns nodes and add a view more btn to load more of them if requested

Users should be able to delete a component (pipeline/task/resource)

We should pass to the startDialog a valid model and work with that

#51 (comment)
#51 (comment)

When user double-clicks on a Tekton resource the tree gets expanded/collapsed. We should also open the resource YAML in the editor.

Add an action so user can explicitly ask for logs related to a pipelinerun/taskrun and maybe show them during execution

We should add integration tests so that we can validate that changing the CLI version does not impact the experience.
We could follow what has been done for the IntelliJ OpenShift Connector (https://github.com/redhat-developer/intellij-openshift-connector) with the fact that we need to check on upstream Kubernetes and also on OpenShift. For Kubernetes, we can use Kind (https://kind.sigs.k8s.io/docs/user/quick-start/) as Travis provides a Docker env by default.

We should use the latest version of CLI as each release comes with new features

https://stackoverflow.com/questions/34176607/custom-deserialization-of-list-using-jackson

Update APIs to support v1beta1 and also remove deprecated attributes from snippets.

When expanding a namespace node and the list of tasks is retrieved this error is printed

java.io.IOException: Process exited with an error: 1 (Exit value: 1) Error: unable to match a printer suitable for the output format "'jsonpath={range .items[*]}{.metadata.name}{'\n'}", allowed formats are: go-template,go-template-file,json,jsonpath,jsonpath-file,name,template,templatefile,yaml

PipelineRuns can be standalone without referencing a pipeline and should be displayed in their own folder, in addition to under a particular pipeline

Add pipeline preview diagram for pipelineruns with color coding for the status of the tasks that are executed or are in progress. Here are the available statuses:
https://github.com/tektoncd/pipeline/blob/master/pkg/apis/pipeline/v1alpha1/taskrun_types.go#L193

When editing a YAML, user should be able to generate snippets for the trigger types using vscode code completion. The trigger types are:

• TriggerTemplate type
• TriggerBinding type
• ClusterTriggerBinding type
• EventListener type

Pipeline YAML could be long and complex which makes it difficult to get an overview of all tasks included in the pipeline and their execution order. It would be beneficial to be able to get a read only visual graph of the pipeline based on the YAML to help user rapidly understand the tasks and how they'd execute.

Users should be able to run a pipeline by using the extension

When there are resources available, user has the feeling one is selected on the UI but task can't be started

We need to add a refresh action so user can explicitly ask to reload the selected node

This is related to redhat-developer/vscode-tekton#144

PipelineRun and TaskRun are immutable objects and cannot be edited after they are created. If user opens these objects form the tree in the editor, they should be opened as read-only.

Forcing the user to specify the namespace is annoying and counter productive because most of the samples don't specifiy it. We should save it in the callback context and retrieve it when we push to the cluster.

If i have a string (which contains a value with a space) in an array and the array is passed as value to the pipeline, it is unable to start.

Error: Process exited with an error: 1 (Exit value: 1) Error: param '"message' not present in spec

The Tekton Pipelines tree currently requires a manual refresh to display the latest state of the pipelines and pipelineruns. This would leave the user thinking the pipeilnerun is running for a long time.

List of runs can grow over time. To avoid this we should display the first 5 elements and add a Show More btn, so user can see more items upon request

There are multiple icons which are different between this plugin and vscode extension. We should use the same set of icons in both.

By using this yaml

spec:
  params:
    - name: flags
      type: array
    - name: someURL
      type: string
  steps:
    - name: build
      image: my-builder
      args: ["build", "$(params.flags[*])", "url=$(params.someURL)"]

the saving fails with this error

io.fabric8.kubernetes.client.KubernetesClientException: Error while performing the call to https://api.crc.testing:6443/apis/tekton.dev/v1alpha1/namespaces/pipeline-test/tasks/. Response code: 500
	at io.fabric8.kubernetes.client.dsl.internal.RawCustomResourceOperationsImpl.makeCall(RawCustomResourceOperationsImpl.java:582)
	at io.fabric8.kubernetes.client.dsl.internal.RawCustomResourceOperationsImpl.validateAndSubmitRequest(RawCustomResourceOperationsImpl.java:593)
	at io.fabric8.kubernetes.client.dsl.internal.RawCustomResourceOperationsImpl.create(RawCustomResourceOperationsImpl.java:122)
	at com.redhat.devtools.intellij.tektoncd.tkn.TknCli.createCustomResource(TknCli.java:171)

Now, by trying it with the terminal i got a clearer message

Internal error occurred: admission webhook "webhook.tekton.dev" denied the request: mutation failed: cannot decode incoming new object: json: unknown field "params"

All of this to say.... we should show an error which is more explanatory

It would be great if yaml completion showed the list of tasks or resources available when the user is filling the task/resource field in the editor.

The extension only has the start action. We need to add the start last run to allow executing last run automatically

Looking at the VSCode extension i didn't find any action related to this but i think it could be useful to have a create btn which opens up an editor with a pipeline/task template to be completed.

Users should be allowed to check the pipeline configuration inside the ide

This has 2 aspects:

• make sure proxy is used when downloading CLI
• make sure proper env variables are set when launching CLI

See redhat-developer/intellij-openshift-connector#170 as an example implementation.

If i have multiple tabs opened and i click Open In Editor on a resource which has a tab already opened, that tab is not highlighted. The focus stays on the current visible tab and it seems the action is not working.

Tekton Triggers enable creating webhooks for pipelines and include the following CRs:

• TriggerTemplate
• TriggerBinding
• ClusterTriggerBinding
• EventListener

The trigger CRD should be displayed in the Tekton window

We need to add some documentation (README..) to explain what is possible to do with this plugin

Add support for selecting multiple resources and deleting them together.

We should ask help to the UX team how we should deal with this. Better stick with the current dialog format or change it to a table view?

We should use the async structured model provided by IJ as it provides better support for refresh, async operations. See the intellij-kubernetes as a template

When editing a YAML, user should be able to generate snippets for conditions using code completion. The snippets are

Condition type
Condition reference in a taskref e.g.

- name: list-pipeline-repo-files-1
      taskRef:
        name: list-pipeline-repo-files
      conditions:
        - conditionRef: "verify-no-file-exists-without-resource"
          params:
            - name: "path"
              value: "$(params.path)"

Tekton conditions enable conditional execution of tasks in a pipeline. Conditions should be added in the Tekton window in the tree to allow user to view and edit them.

See this example:

Currently the form to start a task only allows user to set input params/resources and outputs value. We should add support to declare workspaces

If you have a pipeline which has a task and its name contains one or more uppercase char (or any other invalid char) the taskrun (connected to the pipelinerun) will not be created and no message will be given to the user.
Looking at the log using oc.

Warning  TaskRunCreationFailed  50m                 pipeline-controller  Failed to create TaskRun "pipeline-test-release-run-lktb6-taskName-rjn2r": TaskRun.tekton.dev "pipeline-test-release-run-lktb6-taskName-rjn2r" is invalid: metadata.name: Invalid value: "pipeline-test-release-run-lktb6-taskName-rjn2r": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')

This is related to #34 . We need to check the yaml before to push it. In this particular case we don't even get any error displayed in the ui. Even if you start the pipeline from the terminal you won't receive any error.

If you dont have the "tkn" binary yet, the tooling is offering to do so. The user is asked to confirm downloading it. If the user chooses to do so he/she gets a modal progress dialog which reports the progress of the downloading. This modal progress dialog is preventing him/her from doing anything else. Ideally this task should be put into background so that the user can continue doing stuff.

The tree only supports Namespace and Task nodes. We need to add those other items and list them on tree. Not sure if we also need to create nodes for volume/workspaces (maybe in future??)