Comments

Intresting approach, it would clearly simplify my approach but leveraging modulpath customization and creating a common custom modules location on the "production" repository. My concern is about the fileserver.conf ...(more)

I don't see anything wrong with the above structure but I'm not sure what you're trying to achieve with the sitespecific stuff and yumcustom/ etc. You'd be better off having a single yum module that you simply pass in parameters to with hiera or your ENC. That way you reduce duplication.

I get a feeling that you'll end up with multiple copies of your yum module and have a nightmare managing this in the future. Our entire structure is just /etc/puppet/environments/$environment/ and we rely on Hiera to set params so ...(more)

Comments

Actually the site-specific modules call the forge modules and implements hiera based parameters via a parameterized class. This way I can implement base configuration via the hiera defaults and use ...(more)