Proposal: Common Expression Language Custom Task (CELRun) about community HOT 7 CLOSED

+100

This would be useful to simplify how we use conditions today in dogfooding, so I'd be happy to start running the custom task controller in dogfooding from the experimental repo.

from community.

+1, happy to co-own and help update and contribute cel-task as a base (or start from scratch if that's better).

🎉

from community.

+1, happy to co-own and help update and contribute cel-task as a base (or start from scratch if that's better).

yes yes, we can build on it, thanks for your contributions @imjasonh!

some changes I propose we make include:

• when the CEL expression is valid and is evaluated successfully, the ConditionSucceeded in status of the CELRun is set to True regardless of the expression evaluation result and the CELRun produces a Result representing the expression evaluation result (True/False)
• when the CEL expression is invalid or any other error is encountered, the ConditionSucceeded in status of the CELRun is set to False

this will allow us to distinguish between errors and the expression evaluating to false, which was one of the issues with Conditions

from community.

some changes I propose we make include:

Yeah those both sound like good improvements. 👍

from community.

thanks for the quick review @imjasonh and @afrittoli

created the project folder in tektoncd/experimental#691

from community.

Common Expression Language Custom Tasks is available in https://github.com/tektoncd/experimental/tree/master/cel

from community.

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.

from community.