Bug 1897043 - ordered-values.yaml not honored if values.schema.json provided
Summary: ordered-values.yaml not honored if values.schema.json provided
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.6.z
Assignee: Rohit Rai
QA Contact: Gajanan More
URL:
Whiteboard:
Depends On: 1886861
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-12 07:21 UTC by Rohit Rai
Modified: 2021-01-15 12:22 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1886861
Environment:
Version: 4.6.0-0.nightly-2020-10-03-051134 Cluster ID: d189d8ef-1961-4aff-b73c-afbf2ead94ff Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.121 Safari/537.36
Last Closed: 2020-12-14 13:50:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 7175 0 None closed [release-4.6] Bug 1897043: add support for customSchema in resource sidebar for helm charts 2021-02-03 04:25:04 UTC
Red Hat Product Errata RHSA-2020:5259 0 None None None 2020-12-14 13:51:07 UTC

Description Rohit Rai 2020-11-12 07:21:41 UTC
+++ This bug was initially created as a clone of Bug #1886861 +++

Description of problem:
Order of parameters with comments can be specified via ordered-values.yaml.  This is required when installing via YAML view as need way to have comments with parameters (i.e. Provided link to license accepting via comment).  In 4.6 support for 'Form View' was provided if specify values.schema.json, but user can still switch to 'YAML View'.  Need comments and parameter order to be maintained in 4.6 if switch to 'YAML View' - honor ordered-values.yaml which is NOT happening..


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


How reproducible:


Steps to Reproduce:
1. Log into 4.6 nightly build cluster
2. Navigate to Developer Catalog -> +Add -> Helm Chart
3. Select Ibm Oms Ent Prod v5.1.0 chart
4. Click 'Install Helm Chart'
5. Switch to 'YAML View'

Actual results:
See parameters from values.yaml in alphabetical order without comments

Expected results:
See parameters in defined order in ordered-values.yaml with comments

Additional info:

--- Additional comment from Stephen Cuppett on 2020-10-09 16:56:11 UTC ---

Setting target release to the active development branch (4.7.0). For any fixes, where required and requested, cloned BZs will be created for those release maintenance streams where appropriate once they are identified.

--- Additional comment from  on 2020-10-14 11:41:18 UTC ---

Alternative to supporting ordered-values.yaml would be to be consistent with operator CR approach where schema is shown on right side when using YAML view install (see attachment)

--- Additional comment from  on 2020-10-14 11:42:06 UTC ---



--- Additional comment from Rohit Rai on 2020-10-20 17:10:38 UTC ---

Agreed, having a schema viewer along with YAML editor would make the experience consistent with operator backed forms.

--- Additional comment from Andrew Ballantyne on 2020-10-23 17:17:56 UTC ---

Tracked in Jira for planning purposes: https://issues.redhat.com/browse/ODC-5041

--- Additional comment from Rohit Rai on 2020-11-12 07:19:53 UTC ---

Verified on 4.7.0-0.nightly-2020-11-12-005200

Comment 3 Gajanan More 2020-12-09 05:55:46 UTC
Verified the bugzilla:
Build:4.6.0-0.nightly-2020-12-08-021151
Browser: Google Chrome Version 87
Marking this as verified

Comment 5 errata-xmlrpc 2020-12-14 13:50:52 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 (Moderate: OpenShift Container Platform 4.6.8 security and 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.

https://access.redhat.com/errata/RHSA-2020:5259


Note You need to log in before you can comment on or make changes to this bug.