Design and implement paused Task execution until condition is met

[abayer]

Expected Behavior

A Task can be configured to not commence execution until a condition, such as a particular value being present in the TaskRun's metadata, is true.

• This should be generic enough that the reason for commencing execution can be anything, e.g. it could be triggered by a user pushing a button in a UI, it could be a slack command
• It must be possible to ensure that the mechanism that is commencing execution is authorized to do so (e.g. via a token)

Actual Behavior

Tasks always run to completion or failure

Additional Info

This would enable building features like manual approval or automated quality gates in higher-level applications utilizing Build Pipeline, rather than requiring that any specific "wait until X is true before executing this Task" functionality be built directly into the CRDs.

...this is my first attempt at creating an issue here, so feel free to rewrite as needed. =)

[bobcatfish]

Thanks for writing this up @abayer !

Would you see yourself expressing this at the level of the Pipeline or the Task itself? (I'm thinking Pipeline?)

[abayer]

Hmm. Good question. As part of the Pipeline reference to the Task does feel logical when I think about it. The Task could be used in multiple Pipelines that may not always all want the constraint. Good catch, thanks!

[bobcatfish]

@abayer do you see this as being a subtask of #27 or do you think this issue addresses separate concerns?

[abayer]

@bobcatfish Feels different to me - #27 is "should this Task execute at all" while this is "when should this Task execute". But I could be wrong.

[bobcatfish]

@bobcatfish Feels different to me - #27 is "should this Task execute at all" while this is "when should this Task execute". But I could be wrong.

Makes sense @abayer ! I also updated the description here with some requirements that @demobox shared with me, i.e. that pausing and resuming is really about async execution in general

[demobox]

I also updated the description here with some requirements that @demobox shared with me

Thanks, @bobcatfish! Happy to elaborate on those if useful

[bobcatfish]

Happy to elaborate on those if useful

Always @demobox :D :D :D

[hrishin]

hey @abayer @bobcatfish @demobox

Would you see yourself expressing this at the level of the Pipeline or the Task itself? (I'm thinking Pipeline?)

Considering this would it be fine to declare "wait until condition" at pipeline task (just like RunAfter) level rather task definition?

Could you please shed some light on this?

[naiduasn]

Hey, just want to check if we would see this getting implemented anytime soon.