Description of problem:
When using the `default` property in a Pipeline param, it prevents the UI from creating a PipelineRun due to it straight copying the params and `default` is not a valid property in a PipelineRun params.
Version-Release number of selected component (if applicable):
4.2.14 of OpenShift Console
100% when Pipeline params has a `default` property. Otherwise not an issue.
Steps to Reproduce:
1. Create a Pipeline with a param that includes a `default` property
2. Try to start the Pipeline
There is no UI update / error. The UI does nothing when the Pipeline is trying to be started. The PipelineRun is not created.
The PipelineRun to be created and thus starting the Pipeline. Shouldn't have an issue with `default` in Pipeline params.
Jira issue: https://issues.redhat.com/browse/ODC-2719
Became a blocker from PM's point of view when we investigated and found that even without a `default` the params provided a `default` with the value the user enters in the UI... thus causing the issue 100% anytime using Pipeline params.
Created attachment 1662610 [details]
Showing the parameters without any error
I have validated the bug on
Build:4.3.1 (This is the RC build)
Browser: Google Chrome Version 78.0.3904.108 (Official Build) (64-bit)
Please find the attachment where you can see the output when user provides multiple parameters.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.