Pipeline Service should be able to handle params

[emmjohnson]

As an operator, I want to be able to write values into the pipeline which are picked up by the runTemplate.

AC

Given a pipeline, CRD
When a value is written into the inputs field
And the runTemplate refers to that field
Then the object is stamped out with value in that field defined.

apiVersion: kontinue.io/v1alpha1
kind: Pipeline
metadata:
  name: tests
spec:
  runTemplateName: tekton-runner # use the `RunTemplate` named ‘tekton-runner’ to
                                 # figure out how to stamp out “*Run” objects that
                                 # represents “running” (e.g. tekton/PipelineRun)

  inputs:                        # at the moment, you can pass anything to this field,
    url: http://git.dev/d3adb33f.tgz     # but it could (should?) be something
                                         # strongly typed

---

apiVersion: kontinue.io/v1alpha1
kind: RunTemplate
metadata:
  name: run-with-source
  labels:
    app.tanzu.vmware.com/type: test 
spec:
  completion:
    succeeded: {key: 'status.conditions.#(type=="Succeeded").status', value: "True"}
    Failed: {key: 'status.conditions.#(type=="Succeeded").status', valueNot: "True"}

  template:
    pipelineRef: 
      name: my-tekton-pipeline                   # <= (1)
    workspaces:
      - name: shared-data
        volumeClaimTemplate:
          spec:
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 5Gi
    params:
      - name: blob-url
        value: '$(pipeline.spec.inputs.url)'    # <= (2)

would result in an object

spec:
  workspaces:
    - name: shared-data
      volumeClaimTemplate:
        spec:
          accessModes:
            - ReadWriteOnce
          resources:
            requests:
              storage: 5Gi
  params:
    - name: blob-url
      value: http://git.dev/d3adb33f.tgz

Notes:

The top level field should be called Inputs. This field should be a map[string]JSONobject.

Out of scope

Default values

[DanieldeR]

As discussed during pre-IPM: for beta the scope of this issue should just feed into Tekton params. We should have an additional field called input that aligns wth the examples in https://github.com/vmware-tanzu/cartographer/blob/4c0071527b8d53c6e25a37b43a3211a5d7ebd3a0/experiments/pipeline-service/examples/05-complete-supply-chain/app-operator/supply-chain-templates.yaml and https://github.com/vmware-tanzu/cartographer/blob/4c0071527b8d53c6e25a37b43a3211a5d7ebd3a0/experiments/pipeline-service/examples/04-simple-supply-chain/operators/supply-chain-templates.yaml

[squeedee]

Can we be clear that this story introduces Inputs and Params or add an 'Inputs' story?

[emmjohnson]

I wrote a kuttl test here - 81-pipeline-params, but have not had time to make it any further. Putting this back in To Do in case someone can pick it up.

[waciumawanjohi]

81-pipeline-params includes implementation of Input with a specified field named params. This is not required by the story, and users will be empowered to choose their own field names if we remove this params field in favor of a map[string]JOSNobject