tektoncd / tektoncd/pipelines-as-code
Let a user specify a "remote" file for CEL
Open
Nobody has claimed this yet.
design
feature
priority/medium
- Dominant language
- Go
- Stars
- 214
- Forks
- 144
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 27
Description
Instead of having to specify the full CEL expression into the annotations (which doesn't scale) we could have a syntax that would reference a remote reference to a file containing the full CEL.
This would allow to write and share long CEL filtering across pipelirun or repository.
example:
pipelinesascode.tekton.dev/on-cel-file: .tekton/file.cel # resolve .tekton/file.cel at the same revision time where the event is triggered.
pipelinesascode.tekton.dev/on-cel-file: https://raw.github.com/foo/bar/.tekton/file.cel # http get of the file
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how pipelines-as-code reads CEL annotations and resolves the event's revision. Compare the proposed .tekton/file.cel path with the HTTPS URL example, then verify that both forms load the full expression at the intended revision and that the existing inline annotation behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100