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.