Project

General

Profile

Actions

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.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Web Interface
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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 issues 3 (1 open2 closed)

Related to Foreman - Feature #3260: Allow puppet parameters to have no default value, but overrideableClosedOri Rabin10/15/2013Actions
Related to Foreman - Feature #3309: Support deep merging of hash structures in smart class parametersClosedOri Rabin10/17/2013Actions
Blocks Foreman - Tracker #4470: Usability of parameters and overridesNew

Actions
Actions

Also available in: Atom PDF