Pipeline: FR: Allow Resources to be declared as "optional"

Created on 30 Apr 2019  路  5Comments  路  Source: tektoncd/pipeline

Expected Behavior

Task authors should be able to declare some Inputs as "optional".

Actual Behavior

Today all declared input resources must be supplied.

kinfeature
Source
picture dlorenc
👍2

Most helpful comment

Example use-cases:

  • A "deployment" task that can deploy to a specified cluster, but defaults to the cluster it is running in.
  • A task that can optionally upload artifacts to an artifact store, but does not need to.
picture dlorenc on 30 Apr 2019
👍3

All 5 comments

Example use-cases:

  • A "deployment" task that can deploy to a specified cluster, but defaults to the cluster it is running in.
  • A task that can optionally upload artifacts to an artifact store, but does not need to.
dlorenc picture dlorenc on 30 Apr 2019
👍3

/assign pritidesai

pritidesai picture pritidesai on 24 Sep 2019

/kind feature

vdemeester picture vdemeester on 7 Nov 2019

gke-deploy Task in the catalog could use this functionality: https://github.com/tektoncd/catalog/pull/126

That task would ideally be able to accept either a cluster resource OR the necessary args to configure access to that cluster. Very similar to the first example use case mentioned by @dlorenc

sbwsg picture sbwsg on 12 Nov 2019

Design Doc: https://docs.google.com/document/d/1oe936Zspc8jL9Tb7kWd26bS6sf2emxUxTjt-aKv01Mc/edit#heading=h.duu98lpb6lg4

pritidesai picture pritidesai on 15 Nov 2019
Was this page helpful?
0 / 5 - 0 ratings

Related issues

silverlyra picture silverlyra  路  4Comments
nader-ziada picture nader-ziada  路  4Comments
r0bj picture r0bj  路  3Comments
andydude picture andydude  路  3Comments
ImJasonH picture ImJasonH  路  4Comments