Bug 1808402

Summary: Helm Install form should have yaml editor to configure the helm release using values.yaml
Product: OpenShift Container Platform Reporter: Rohit Rai <rorai>
Component: Dev ConsoleAssignee: Rohit Rai <rorai>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, cvogt, gamore, nmukherj
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1808404 (view as bug list) Environment:
Last Closed: 2020-07-13 17:22:21 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: 1808404    
Attachments:
Description Flags
yaml editor none

Description Rohit Rai 2020-02-28 12:20:29 UTC 
Description of problem: The current Helm Install form only has one field for release name. In order to configure the install we need a way to provide users with option to configure values.yaml for a chart release.


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


How reproducible:
Always

Steps to Reproduce:
1. Go to Add page and select from catalog.
2. Check the helm charts filter and select a chart to install.


Actual results:
Helm install form has only one form field for release name.

Expected results:
It should also show a yaml editor with default values for the chart dumped in.

Additional info:
Comment 3 Gajanan More 2020-03-10 09:11:09 UTC 
Created attachment 1668833 [details]
yaml editor
Comment 4 Gajanan More 2020-03-10 09:12:31 UTC 
I have validated this bug on 
Build: 4.5.0-0.ci-2020-03-10-023720
Browser: Google Chrome 78.0.3904.108
Marking this bug as verified.
Comment 6 errata-xmlrpc 2020-07-13 17:22:21 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