Commit Graph

12 Commits

Author SHA1 Message Date
chris lawrence
4d8fb68775 updating auth 2020-06-09 08:46:05 +01:00
christopher.lawrence
2d6f08fcce added in and tidy up of metrics 2020-03-30 17:08:13 +01:00
christopher.lawrence
5f78f7fe04 adding in docker and configs 2020-03-27 10:34:40 +00:00
christopher.lawrence
5985bd1450 setting up the wonderful cisbench and facter cache modules for securing my platforms in a lovely way 2020-03-06 14:04:38 +00:00
christopher.lawrence
c590904313 fixed issues with modules and autosign errors 2020-03-04 15:46:25 +00:00
christopher.lawrence
82d7106962 updating hiera to enable role data to true for module deployment 2020-02-06 09:24:11 +00:00
christopher.lawrence
c2faa35b17 adding in the ntp server hiera data 2020-02-05 15:44:56 +00:00
christopher.lawrence
097d1e6884 updated hiera data selinux and ssh 2020-02-05 12:31:52 +00:00
christopher.lawrence
1d55cd96ce added hiera data for nameservers and configured resolv profile 2020-02-04 14:53:53 +00:00
christopher.lawrence
bd5a987e92 adding dns and ntp modules 2020-02-04 14:30:32 +00:00
christopher.lawrence
b134faf785 configuring hieradata for puppet server role 2020-02-04 13:48:53 +00:00
Reid Vandewiele
7264b63d10 Enable Hiera 5
This commit enables the control repo to use Hiera 5 environment-level
hiera hierarchy. This means adding a hiera.yaml to the repo, and moving
hieradata/ => data/.

We should do this to the control-repo template new customers base off of
because in a Hiera 5 world, the global hiera.yaml should be very minimal
(possibly even ONLY having the console level), and everything else
(nodes, common) belongs in the environment hiera.yaml.

This control-repo template is how people start using Puppet. It should
reflect using our most modern technologies.
2017-11-15 09:24:40 -08:00