Ways to simplify configs?

Alan DeKok aland at deployingradius.com
Thu Jul 27 15:49:36 CEST 2017

On Jul 27, 2017, at 8:06 AM, Jonathan Gazeley <Jonathan.Gazeley at bristol.ac.uk> wrote:
> Puppet *can* push out subdirectories, recursively. However it's not recommended to do it that way. Puppet's strength is modelling everything as a resource that can be manipulated in order to generate configs, rather than directly storing the configs itself. Flat files don't really tie into this.

  Puppet should be able to have recursive dependencies.

  i.e. create a directory hierarchy from a set of config files / templates / variables.  Then, sync the directory hierarchy to a new machine.

> Hence I wrote my FreeRADIUS Puppet module which allows the user to define things in a native Puppet way, and the module then magically generates the config. It's not quite as flexible as editing the plain text files but it has enough flexibility for 95% of people's needs, and it still provides the option to feed in arbitrary plain text configs for the cases where the content can't be modelled in Puppet.

  Sure, that makes sense.

  Alan DeKok.

More information about the Freeradius-Users mailing list