+++ This bug was initially created as a clone of Bug #1951043 +++
Description of problem:
The Start Pipeline Modal does not respect an empty string ('') as a valid default although it is upstream. The UI should not make it a required field in the modal.
Version-Release number of selected component (if applicable):
Always (create via YAML or CLI)
Steps to Reproduce:
1. Create a Pipeline with an empty string default value (see additional info for suggestions how to do it in the UI)
2. Using the actions (or "more options" menu on the list page) select "Start Pipeline"
3. Try to submit with a empty string default param without touching the field
We show * next to the parameters that don't have defaults. An empty string ('') is a falsy value and thus got confused as a no default provided. This is not valid upstream and needs to change.
Should be able to submit without updating any params that have defaults of an empty string ('').
The Pipeline Builder currently doesn't support this and our UI does not allow for empty strings. Will need UX to fix that portion, but the work around would be to use the Pipeline Builder entirely and then flip over to the YAML to set the default of a param to '' and then create via YAML.
--- Additional comment from Andrew Ballantyne on 2021-04-19 13:38:26 UTC ---
Original discussion occurred on Google Chat, but I'm not sure I can link to the specific thread :(
--- Additional comment from Andrew Ballantyne on 2021-04-19 13:40:51 UTC ---
This might be the best link I can get: https://chat.google.com/room/AAAApNTFPIc/aeqy5NztVhw
Created attachment 1791465 [details]
Start Pipeline Modal Parameters accept empty string defaults
Verified on build version: 4.7.0-0.nightly-2021-06-12-151209
Browser: Google Chrome 89
OpenShift engineering has decided to not ship Red Hat OpenShift Container Platform 4.7.17 due a regression https://bugzilla.redhat.com/show_bug.cgi?id=1973006. All the fixes which were part of 4.7.17 will be now part of 4.7.18 and planned to be available in candidate channel on June 23 2021 and in fast channel on June 28th.
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 (OpenShift Container Platform 4.7.18 bug fix update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.