On 6/17/17 7:06 PM, Rob Nelson wrote:
> Jtc,
> 
> I keep my templates and files in the profile class itself, in paths like
> files/phpMyAdmin/config.php and templates/randomapp/app.conf.erb. I have
> a site_config module that has some files that aren't tied to profile
> development, like certs. Other than that, I DO put config files in the 2
> component modules that are private (everything else is from the forge). 
> 
> I hope that gives you some ideas. 
> 
> On Sat, Jun 17, 2017 at 2:41 PM J.T. Conklin <[email protected]
> <mailto:[email protected]>> wrote:
> 
> 
>     Over the past year or so, we've completed a transition from locally
>     developed puppet modules containing node-specific configuration, to
>     using the roles/profiles pattern with parameterized modules with most
>     config values coming from hiera.
> 
>     One exception to this are config files that are too specific, to
>     complicated, or otherwise not suitable for conversion to templates.  At
>     the moment, these are still in our puppet modules.  Not only does this
>     bind node-specific configuration in with otherwise independent modules,
>     now that all our other node-specific configuration is done with hiera,
>     the config is split across two places -- which makes it hard to under-
>     stand.
> 
>     I spent some time look for articles and blog posts that cover this, but
>     all the examples I've seen show use cases where module configuration is
>     completely taken from hiera. How do others handle this?  Store files in
>     the profiles module itself?
> 
>     Thanks in advance,
> 
>         --jtc
> 
>     --
>     You received this message because you are subscribed to the Google
>     Groups "Puppet Users" group.
>     To unsubscribe from this group and stop receiving emails from it,
>     send an email to [email protected]
>     <mailto:puppet-users%[email protected]>.
>     To view this discussion on the web visit
>     
> https://groups.google.com/d/msgid/puppet-users/87a856sbhk.fsf%40wopr.acorntoolworks.com.
>     For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> Rob Nelson
> 

Hi,

I do something similar by keeping files and templates in profiles module
and encode the name of the profile into the path.

So for profile 'foo' I might have profile/templates/foo/ and
profile/files/foo/ that would each contains templates and files,
respectively.

Best regards,
-g

-- 
Garrett Honeycutt
@learnpuppet
Puppet Training with LearnPuppet.com
Mobile: +1.206.414.8658

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/49c65d38-232d-7f1f-24c3-bc9e767ee32a%40garretthoneycutt.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to