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:
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.
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)
Created attachment 1721446 [details] Screen shot of schema display during operator CR install via YAML view
Agreed, having a schema viewer along with YAML editor would make the experience consistent with operator backed forms.
Tracked in Jira for planning purposes: https://issues.redhat.com/browse/ODC-5041
Verified on 4.7.0-0.nightly-2020-11-12-005200
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.7.0 security, bug fix, and enhancement 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:5633
Updated the Doc_text field for the Release Notes.