I couldn't get hiera integrated with PE 3.0.1 to work with nested
hierarchies, so this is what my hierarchy looks like:
:hierarchy:
- defaults
- %{clientcert}
- %{domain}
- %{osfamily}
- %{environment}
- global
Regards,
Alex
On Tuesday, March 19, 2013 2:30:16 PM UTC-7, Larry Fast
I use Netgroups (with LDAP as backend) to group my nodes.
Netgroups is an old NIS thing, which works beautifully. You can group
hosts, and each netgroup, can contain other netgroups, users or hosts.
This way, a host can be a member of several netgroups - and I use netgroup
membership to
On Fri, Mar 22, 2013 at 04:22:19PM -0700, Aaron Mills wrote:
The biggest pain point for us is that having hiera + puppet in the
same repo feels like extra work. If they're going to live
together, why even use hiera? Why not just set variables at the
node level?
For me, here are some reasons
On 25 March 2013 10:12, Robin Lee Powell rlpow...@digitalkingdom.orgwrote:
On Fri, Mar 22, 2013 at 04:22:19PM -0700, Aaron Mills wrote:
The biggest pain point for us is that having hiera + puppet in the
same repo feels like extra work. If they're going to live
together, why even use
Late to the party, but wanted to add my $.02
We also keep hiera, manifests, and modules in a single repository at the
moment. Since we use dynamic environments for development (as outlined
here: https://puppetlabs.com/blog/git-workflow-and-puppet-environments), we
also have a node-level
Hi Andy,
I guess my most important request for Hiera 2 is diagnostic information.
It's probably a broader request for better diagnostics in puppet as a
whole. Here's what I dream of ...
1. The ability to run Puppet on the puppetmaster using the cached Facts
from a server.
2. A postmortem
