Feature: method to absorb git-source yaml into Pipeline/Task $inputs etc

[bitsofinfo]

I'd like for devs to be able to configure some aspects of the pipeline behavior via YAML that lives in the cloned git source that Tekton treats as an input resource (currently).

I.E. some way I could"absorb the contents of this yaml file into the Pipeline's scope of available variables that can then by used via some sort of tekton $inputs.[yamldoc].prop1.subitem2.key, then you could just reference that data w/ CEL expressions anywhere in Tasks.

Similar to the whole task results functionality and task inputs. Something that could just source a structure from a yaml file that then becomes useable as $(yamlsource.parent.list[0].name) whatever.

Right now to do this I'm having to manually read this YAML then traverse it and turn it into a bunch of Task result files on the shared volume which seems clunky.

[ghost]

I'm not entirely clear what's being requested. Could you show a more complete Pipeline example to demo what you're trying to achieve? Or sketch out some YAML of the interface you'd like to see?

[bitsofinfo]

1. YAML in a git-source

x: "dog"
y:
  key: "name"
b:
- name: x
- name: y

2. Something in tekton that can consume this and assign it to some varname

3. Then I can reference it in any task/pipelines via: $(inputs.varname.x) and $(input.varname.y.key) or $(b[0].name)

How/what its keyed under and accessible via the $() syntax, I'm not sure inputs? or some other key etc. Would be great to use CEL expression over these as well.

[jlpettersson]

I understand your problem. We had the same problem when adopting Tekton, and we created our own pipeline.yaml abstraction that can live in the code repository and then we have a Task that parse the pipeline.yaml and generate a Tekton Pipeline and initiates a PipelineRun.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[bitsofinfo]

/reopen

[tekton-robot]

@bitsofinfo: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[bitsofinfo]

/remove-lifecycle rotten

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
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.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[vdemeester]

/remove-lifecycle stale

[tekton-robot]

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.

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
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 rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.