Bug #4424
closed
Strikeout of Puppet Class Properties when Overriding on Node not working
Added by Stephen Herd about 10 years ago.
Updated almost 6 years ago.
Description
Since 1.4, it appears that when you override a Puppet Class Property, the original value doesn't get struck out anymore. This makes it difficult to tell what values have and have not been overridden at a quick glance when looking at a node.
- Category set to Web Interface
- Priority changed from High to Normal
- translation missing: en.field_release deleted (
5)
- Related to Tracker #4470: Usability of parameters and overrides added
Also, since the parameter doesn't get struck out it is overridable numerous times.
- Related to Bug #4623: Override button for Puppet class parameter can be clicked more than once added
- Bugzilla link set to https://bugzilla.redhat.com/show_bug.cgi?id=1106944
- Related to Bug #8786: Override button is gone and won't be back added
- Assignee set to Tom Caspy
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2072 added
- Pull request deleted (
- Has duplicate Bug #9268: overridable parameters continue to show up after being overridden added
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- translation missing: en.field_release set to 28
- Bugzilla link deleted (
1106944)
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by