Bug 1813707

Summary: Pipeline Builder - Handle Array Parameters
Product: OpenShift Container Platform Reporter: Andrew Ballantyne <aballant>
Component: Dev ConsoleAssignee: Andrew Ballantyne <aballant>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: medium Docs Contact:
Priority: high    
Version: 4.4CC: aos-bugs, gamore, nmukherj
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: The Pipeline Builder reads Task/ClusterTask definitions and made an incorrect assumption that all Parameters were of type string. Consequence: When a Task Param of type array was encountered, it would cast the array to a string and represent it losing the type and would produce a value to the Task param as string thus breaking the contract with the Task. Fix: Support Array type in the UI and properly retrain the type Result: Managing both types allows the Pipeline Builder to work the way it was intended.
 Story Points: ---
Clone Of:
: 1813884 (view as bug list) Environment:
Last Closed: 2020-07-13 17:20:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1813884    
Attachments:
Description Flags
parameters send to the pipeline none

Description Andrew Ballantyne 2020-03-15 16:21:16 UTC 
Description of problem:
While using the Pipeline Builder, when a parameter of type array is used, it doesn't come out of the builder as type array... but instead of type string. This is a type violation and thus prevents the Pipeline from being started.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create using the Pipeline Builder (create button on the Pipelines list view)
2. Add `openshift-client`
3. See a text input, update, and create Pipeline

Actual results:
The value was saved as a string in the YAML; Pipeline won't start.

Expected results:
The value should be saved as an array.

Additional info:
Comment 3 Gajanan More 2020-03-17 12:41:00 UTC 
Created attachment 1670789 [details]
parameters send to the pipeline
Comment 4 Gajanan More 2020-03-17 12:43:24 UTC 
I have validated the bug on 
Build: 4.5.0-0.nightly-2020-03-16-234954
Browser: Google Chrome Version 78.0.3904.108
Marking this as verified.
Comment 6 errata-xmlrpc 2020-07-13 17:20:05 UTC 
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.

https://access.redhat.com/errata/RHBA-2020:2409