Bug #8217
closed
Matchers/overrides have no clear grouping, mess of input boxes
Added by Dominic Cleal about 10 years ago.
Updated over 6 years ago.
Description
The overrides section of the smart class parameter page has become a bit of a maze of checkboxes and input boxes, and needs tidying up.
The main problems that I see are:
1. "Global" configuration for the behaviour of overrides (merging, "avoid duplicates", order) should be more separate to the list of matchers.
2. No separation between individual matchers, so what the "Use Puppet default" box applies to is unclear. Other forms in the app use horizontal rules to separate individual items.
Files
- Related to Feature #3260: Allow puppet parameters to have no default value, but overrideable added
- Related to Feature #3309: Support deep merging of hash structures in smart class parameters added
- Blocks Tracker #4470: Usability of parameters and overrides added
- Status changed from New to Assigned
- Assignee set to Ori Rabin
3. "Use Puppet default" is below the default value, but above the override value text boxes
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/1898 added
- Pull request deleted (
)
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Translation missing: en.field_release set to 35
Also available in: Atom
PDF