Hello everyone, I am currently working in a Linux team that decided to use Puppet as a configuration management tool and we developed a couple of own modules, use a lot from the forge and we keep hiera data in a separate git repository (tools: r10k+controlrepo, one separate hiera repo not managed by r10k, gitlabs server to manage all git repos)
The IT department is quite big and has different silos (e.g VMWare team, Linux team, Backup team, Storage team, etc) but we (meaning the linux team) want to use puppet to replace workflows that beforehand went through different departments, e.g. to configure backup for a new machine, the backup team had to create a node in their backup tool and than give us the necessary input to generate the correct configuration file on the new server. Ideally I would like them to manage the data in hiera the same way as we do, so they can leverage the hierarchy to define defaults on a subnet level, host level, etc. but on the otherhand access to the single hiera repo would allow them to basically reconfigure everything on a server (like adding data for the sudo module to add custom sudo rules). Even though this would be tracked through git logs, a lot of my collegues are not comfortable with that (and might even be against internal regulations) so I am wondering how you manage the fact when a lot of different teams with different knowledge about puppet, yaml, and git should contribute to hiera but should only manage stuff they care about/are responsible for. - Stefan -- 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/56B12FDC.8090801%40taunusstein.net. For more options, visit https://groups.google.com/d/optout.
