You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using StepTemplates in Steps referencing StepActions, there shouldn't be a validation error if the StepTemplate uses fields that conflict with StepActions (e.g. env)
e.g. The following should work be passed by the validation web hook. After the StepAction is fetched, it should naturally be merged with the underlying StepTemplate.
A web hook validation error is thrown that env cannot be used with ref. This is wrong since the user did not explicitly provide the env with the ref field in the Step. The purpose of StepTemplate is to add values to Steps. This should only happen after the StepAction is fetched and inlined.
Expected Behavior
When using
StepTemplates
inSteps
referencingStepActions
, there shouldn't be a validation error if the StepTemplate uses fields that conflict with StepActions (e.g.env
)e.g. The following should work be passed by the validation web hook. After the StepAction is fetched, it should naturally be merged with the underlying StepTemplate.
Actual Behavior
A web hook validation error is thrown that
env
cannot be used withref
. This is wrong since the user did not explicitly provide theenv
with theref
field in theStep
. The purpose ofStepTemplate
is to add values to Steps. This should only happen after theStepAction
is fetched and inlined.Steps to Reproduce the Problem
kubectl apply -f <above yaml>
Additional Info
Kubernetes version:
Output of
kubectl version
:Tekton Pipeline version:
Output of
tkn version
orkubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'
The text was updated successfully, but these errors were encountered: