This is exactly how we use Foreman & Hiera in our installation... The key thing to set is when configuring the Puppet classes in Foreman, the 'Use Puppet Default' or 'Override' box needs to be checked. This means that if no values are stored in Foreman, then no value will be provided to Puppet, and Puppet will then use Hiera to look that value up.
If you don't check that box, then you run the risk of providing empty strings to Puppet, thereby skipping the Hiera lookup :) HTH Gav On Monday, 10 July 2017 16:44:32 UTC+1, Salty Old Cowdawg wrote: > > In the shop that I code for these days we have The Foreman ENC set up and > running. I want to add hiera to the mix but allow our operations folks the > options the ability to change parameter values using the Foreman GUI. > Given the applications we are having Puppet manage this is rather mandatory > since the values in question get changed often enough to deal with changes > in the operational conditions as they change. Having operators edit hiera > YAML files is not a desired thing. > > I have some ideas for how to implement this but would like some input from > others that may have dealt with the same thing. What I'm looking for is a > coding pattern that says "if foreman is blank, use hiera and if hiera is > blank use this default." > > thoughts anybody? > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/311ba2bb-87a6-4c73-905b-339bed9dd779%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
