Project

General

Profile

Feature #10653

Add smart matchers keyed on config groups

Added by Pat Riehecky over 7 years ago. Updated over 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Parameters
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

From the Foreman 1.9 manual

Note that it isn't possible to use a smart class parameter override with a config group, as a host may have many config groups with no way to define an order of precedence. Overrides should be made on a host group, host or other attribute.

Can an order of precedence be defined, say by attaching an arbitrary integer by hand to the config group (order or priority or whatever), and a warning be emitted (in puppet and forman) be emitted for a host that has a redefinition?

Being able to scope some parameters into the configuration group they belong to would help clarify my workflow. I'm willing to manually unwind any odd redefinitions in exchange for the ability to group things.


Related issues

Related to Foreman - Tracker #4470: Usability of parameters and overridesNew

Related to Foreman - Tracker #12950: Turn all parameters into lookup keysNew2015-12-28

History

#1 Updated by Dominic Cleal over 7 years ago

  • Subject changed from Config Groups, Smart Variables, and Class Parameters to Add smart matchers keyed on config groups
  • Category changed from Puppet integration to Parameters

#2 Updated by Tomer Brisker over 7 years ago

  • Related to Tracker #4470: Usability of parameters and overrides added

#3 Updated by Ori Rabin almost 6 years ago

  • Related to Tracker #12950: Turn all parameters into lookup keys added

Also available in: Atom PDF