What if I want to change apt settings elsewhere? about puppet-elastic_stack HOT 7 CLOSED

this kind of conflicts is where I find puppet very annoying

Absolutely. It really does get better with Hiera and include, though. So it's worth working towards, in my opinion. :)

This video changed my Puppet life, by the way:

https://www.youtube.com/watch?v=v9LB-NX4_KQ

It's old now, but I think it's mostly still relevant.

from puppet-elastic_stack.

Awesome, looking at it right now!

from puppet-elastic_stack.

Closing this old issue which got solved.

The roles & profile pattern says apt is declared in your profile::apt, elastic stuff is in profile::elasticsearch and the latest include the former one. If all nodes that use these modules do it the same way, no need for parameters / automatic parameter lookup.

from puppet-elastic_stack.

Does your environment configure apt with a resource-like declaration, like this?

class {'apt':
  setting => 'value',
}

The more modern approach is to include apt where you need it, and set the apt class parameters with Hiera data. Then, apt can be used by any number of modules with include, require, and contain, and they will all get the parameters from Hiera and not create resource conflicts.

CAUTION: Do not mix include-like and resource-like declarations for a given class. If you declare or assign a class using both styles, it can cause compilation failures.
-- https://puppet.com/docs/puppet/7.4/lang_classes.html#lang_class_declare

from puppet-elastic_stack.

Hello @jarpy
Thanks for the heads-up, I never got hiera working. Maybe I should give it another shot. Though, truth be told, this kind of conflicts is where I find puppet very annoying.

from puppet-elastic_stack.

If you're in a hurry, here's the super-relevant section:

https://youtu.be/v9LB-NX4_KQ?t=2696

from puppet-elastic_stack.

I also, personally, really like the "automatic parameter lookup" mentioned at 51:00, but that's a matter of taste.

from puppet-elastic_stack.