Actions
Bug #9187
closed
Overrideable empty puppet class parameters are still validate their default value
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Description
As promised at dinner last night here is the issue :)
With #3260 it became possible to have puppet class parameters that are overrideable but they still validate their default value. That means a parameter with a default value of ${puppet::params::server} and of type boolean will error out even though the default value is not used.
Updated by Ewoud Kohl van Wijngaarden about 10 years ago
- Related to Feature #3260: Allow puppet parameters to have no default value, but overrideable added
Updated by Ewoud Kohl van Wijngaarden about 10 years ago
For other users: the workaround is to uncheck the 'use puppet default' checkbox, set a valid default, save, uncheck the checkbox and save again.
Updated by Dominic Cleal almost 10 years ago
- Related to Bug #9812: 'match' and 'value' parameters in override value's create should be required in apidoc added
Updated by Dominic Cleal almost 10 years ago
I think #9812 might have made this worse in some cases, as it checks for a value to be present...
Updated by The Foreman Bot almost 10 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2408 added
- Pull request deleted (
)
Updated by Dominic Cleal almost 10 years ago
- Translation missing: en.field_release set to 35
Updated by Ori Rabin almost 10 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 92eb3d7ca920c1b3fb88137c21fc41cfe9194f22.
Updated by Dominic Cleal over 9 years ago
- Related to Bug #11663: Empty lookup value validated even when use_puppet_default is checked added
Updated by Dominic Cleal over 9 years ago
- Has duplicate Bug #12878: Default Puppet parameter from Satellite is still validated if "Use Puppet default" is selected added
Updated by
Actions