Actions
Feature #3260
closedAllow puppet parameters to have no default value, but overrideable
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Description
A puppet default may be fine, but sometimes you want to override this. I don't think it's currently possible to enter no default in foreman itself, but override it on host(group) level.
Updated by Dominic Cleal over 10 years ago
- Related to Tracker #4470: Usability of parameters and overrides added
Updated by Dominic Cleal over 10 years ago
- Bugzilla link set to https://bugzilla.redhat.com/show_bug.cgi?id=1088751
Updated by Ori Rabin about 10 years ago
- Status changed from New to Assigned
- Assignee set to Ori Rabin
Updated by The Foreman Bot about 10 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/1768 added
- Pull request deleted (
)
Updated by Dominic Cleal about 10 years ago
- Target version changed from 1.7.3 to 1.7.2
Updated by Ori Rabin about 10 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 8e53b7c915ecab576e5950b20e75552ec6a02edb.
Updated by Dominic Cleal about 10 years ago
- Related to Bug #8214: "Use Puppet default" column in host parameters list has no data added
Updated by Dominic Cleal about 10 years ago
- Related to Bug #8217: Matchers/overrides have no clear grouping, mess of input boxes added
Updated by Dominic Cleal about 10 years ago
- Translation missing: en.field_release set to 21
Updated by Ewoud Kohl van Wijngaarden almost 10 years ago
- Related to Bug #9187: Overrideable empty puppet class parameters are still validate their default value added
Updated by Dominic Cleal over 9 years ago
- Has duplicate Feature #6061: Allow override to empty values added
Updated by Dominic Cleal about 9 years ago
- Related to Bug #12248: Host[group] parameter form shows default value even when "use puppet default" is selected added
Actions