Closed alex-harvey-z3q closed 7 years ago
That sounds like a good idea! I don't have a preference, but I would consider EPP templates, too.
It's just a matter of what to name the file right? There is nothing to interpolate. If so, .epp
it is.
On second thoughts, EPP breaks Puppet 3 AFAIK and that's not going to help me much because I am stuck on Puppet 3!
@rnelson0 It turns out that this old files source => ...
pattern does not break masterless Puppet in general. I am not sure why I thought it did. I was looking at a strange issue where these files were installed as zero length files and I jumped to the wrong conclusion. I still think the patch I submitted is an improvement, aside from the misleading comment. So I sent another PR to fix the comment.
I think this post here is correct, re masterless puppet and source => puppet:///modules/foo/bar
https://serverfault.com/a/347912/374465
Ok. The issue is that source => ...
breaks a specific implementation of masterless puppet, namely masterless Puppet based on puppet apply --catalog catalog.json
.
I'd prefer to keep going with Puppet 4 and higher standards, as Puppet 3 is EOL.
@stahnma I do plan to upgrade to Puppet 5 very soon, although I am not aware of any other large sites here in Sydney that have upgraded to Puppet 4 yet. Breaking Puppet 3 for people is just going to send more people off into Ansible land IMO.
Is this fixed in 1.3.0? I think we switch the GPG key files to templates.
Yes, my PR that changed the GPG key files to templates was merged.
This module is using the old files pattern to get files from a Puppet Master.
This is a problem because it breaks masterless Puppet, and introduces a dependency on an external system.
I propose to convert those files into ERB templates.
Is that OK?