-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tekton pipeline - parameters are not getting replaced recursively #1524
Comments
Hi @maheshwarishikha, thanks for the issue. Can you share the yamls for your PipelineRun, Pipeline and Tasks ? |
@vdemeester , Thanks for the prompt response. |
Hi @vdemeester , did you get a chance to look at files...? Please do check ...it is like blocker for me and I have tried many things...but no luck yet. Thanks in advance. |
@maheshwarishikha I took a look. This is by design "so far". You have to pass params explicitely to your Task when referencing it. From your file, you need to update your Pipeline to something like the following.
The issue #1484 is tracking discussion wether we should automatically pass parameters (and resources) from pipeline to task if the have the same name. |
@vdemeester , ohh...my bad. I am doing this way only but the files I uploaded does not have that change. Very sorry for the confusion. |
@maheshwarishikha the updated files seems ok too. You are using the same value for the parameter as the default value |
@vdemeester , I get following error - Describing pipeline/task - it shows parameters as $(params.pathToYamlFile) not with their substituted value. |
@maheshwarishikha oh, I think I see what is the problems, (Related issue on the |
@vdemeester , I have tried both...both fails.:( |
It worked finally. Thanks. |
try |
Expected Behavior
After running pipeline-run, parameters value provided in pipeline-run should substitute parameters in Pipeline, then in task and so on.
Actual Behavior
No value is being substituted, hence it is failing with message "$(input.params.pathToYamlFile): No such file or directory"
What could be the reason of this? Is there a way that I can check if there is any syntax error in yaml files.
Kindly help.
Thanks.
The text was updated successfully, but these errors were encountered: