Hi all, It's been a long standing issue that installer users who try to alter Foreman settings end up surprised when those changes get wiped out when they upgrade (by running the installer again). Many things can be set by installer flags, but not all.
Most recently we added the ability to interface directly with Hiera in /etc/foreman/custom-hiera.yaml (https://theforeman.org/manuals/1.14/index.html#advanced-module-configuration) which greatly opens up the configuration to customization. However, there's still a few limitations with this, particularly if you need to instantiate a new resource. A good example is wanting to tune postgresql configuration which uses the `postgresql::server::config_entry` defined type. You can get around it this by using the foreman puppet classes directly and then including a class of your own with the additional config. But what if you want to use the installer? Should we deal with these on a case-by-case basis - maybe make specific postgresql settings accessible in puppet-foreman flags or take a hash of them in the module? The other thing I was thinking - and I'm not sure if this is overkill - is giving the user a directory to dump their own custom puppet modules in, and then using the custom-hiera.yaml feature to include them. Thoughts/ideas would be much appreciated. Thanks Stephen -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
