On 05/21/2014 07:16 PM, Andre Nathan wrote:
> I organize my setup so that hiera looks for my nodes under
> hieradata/nodes/certname.yaml I see no reason not to allow further
> nesting if needed.
>
>
> It may be the only solution for me, but I'd rather not use YAML files as
> the risk
On Wednesday, May 21, 2014 11:44:43 AM UTC-5, Andre Nathan wrote:
>
> On Wednesday, May 21, 2014 1:14:31 PM UTC-3, Garrett Honeycutt wrote:
>
>
>> Your usage of a base node that other nodes inherit is an anti-pattern
>> though and will cause you grief as you grow.
>
>
> Why is it an anti-patte
On Wednesday, May 21, 2014 1:59:09 PM UTC-3, Doug_F wrote:
>
> I organize my setup so that hiera looks for my nodes under
> hieradata/nodes/certname.yaml I see no reason not to allow further nesting
> if needed.
>
It may be the only solution for me, but I'd rather not use YAML files as
the ris
It may be worth it to look more at hiera and adjust your codebase there.
For example my site.pp has one line: hiera_include('classes').
I organize my setup so that hiera looks for my nodes under
hieradata/nodes/certname.yaml I see no reason not to allow further nesting
if needed.
That being said
On Wednesday, May 21, 2014 1:14:31 PM UTC-3, Garrett Honeycutt wrote:
>
> I believe you mean the deprecation of 'import'.
Woops, indeed.
> The easiest way to fix
> this is to cat all of your files together into one site.pp file.
>
Now that's even worse than having all node files in a single
On 5/21/14, 11:45 AM, Andre Nathan wrote:
> Hello
>
> I have a fairly large repository (~100 modules, ~50 classes, ~200
> nodes). It is currently organized like this:
>
> modules/
> apache2/
> manifests/
> files/
> templates/
> iptables/
> manifests/
> files/
