-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Closed
Labels
area/resolutionIssues related to remote resolutionIssues related to remote resolutionkind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.
Milestone
Description
Feature request
Using local resolution, the param substitution is not well applied when using default value inherited from another param value as a fallback.
Use case
In some case, I need to use default value inherited from another param value as a fallback (overridable by a PipelineRun).
apiVersion: tekton.dev/v1
kind: Pipeline
metadata:
name: pipeline-with-default-value-from-param
namespace: jx
spec:
params:
- name: fallback-param
type: string
default: "fallback value"
- name: param
type: string
default: $(params.fallback-param)
We also have the same use case with task.
It's working well with remote resolver when then passing param to task, but not with local resolver. The result value is the litteral $(params.fallback-param). Could this substitution be backported to local resolver ?
Thanks !
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/resolutionIssues related to remote resolutionIssues related to remote resolutionkind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.
Type
Projects
Status
Done