Loading...

XML

Word

Printable

Story Points:
3
Affects:

Documentation (Ref Guide, User Guide, etc.), User Experience
Release Note Text:

Hide
We are now able to access the full body and headers from the template variable and CEL filtering as CEL expression.

This allow to output or filter anything GitHub or others send you in your PipelineRun

Show
We are now able to access the full body and headers from the template variable and CEL filtering as CEL expression. This allow to output or filter anything GitHub or others send you in your PipelineRun
Git Pull Request:
https://github.com/openshift/openshift-docs/pull/68394
[QE] How to address?:
---
[QE] Why QE missed?:
---

Epic Goal

We currently only allow a subset of custom variable (as well as customparams) for the user. This is nice and handle most use cases, but there is a lot in information in payload that may be interesting to use for users.

This would let users to achieve endless customization according to what the Git provider does.
For example they could launch different tasks the labels on PR are different.
We would be able to make it dynamic by making it a CEL expression and let the user do conditional as they wish in there

CI - MUST be running successfully with tests automated
Release Technical Enablement - Provide necessary release enablement details and documents.
...

Acceptance criteria are met
Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
User Journey automation is delivered
Support and SRE teams are provided with enough skills to support the feature in production environment

clones

SRVKP-3510 Make body payload from the Git interface accessible to the user

documents

SRVKP-3510 Make body payload from the Git interface accessible to the user