Step variable validation when using a custom trigger
rejected
C
Cyan Stingray
When using a custom trigger, it is possible to bypass the validation set for a step variable.
For example, if you have a step variable set up with the following input validation: <+input>.regex(^[a-z0-9-]{0,55}$), the validation works as expected when the pipeline is executed manually. However, when the pipeline is triggered via a custom trigger, it can bypass this validation, allowing input values that do not conform to the defined regex pattern.
The pipeline will run without enforcing the validation, and the input value provided by the custom trigger can fail to meet the specified input validation.
Log In
Activity Feed
Sort by
Rohan Gupta
rejected
Rohan Gupta
pending feedback
How are you checking that it reaches the desired validation. Is this jexl validation on the variable?
Have you tried configuring an OPA policy step to check if it conforms? Then you can catch the evaluation after step execution and revert back.