Hello!

This is my first time posting here, and I freely admit I'm a complete 
newbie to Puppet and librarian-puppet.  I briefly had a puppet 3.7.4 
"playground" set up and started learning about coding modules and 
incorporating stuff from the Forge and was starting to work my way into the 
Roles and Profiles pattern, but that's as far as I've gotten with Puppet.

Since my organization has not yet deployed Puppet (we're a month or two 
away from building the environment that will be deployed with Puppet), when 
we saw the release of Puppet 4, we decided it would be better to implement 
Puppet 4 from the start rather than figure out a migration plan later.  At 
the same time, I realized that my original idea of "put all of /etc/puppet 
into a git repo" and keep the forge modules in a separate path wouldn't be 
very maintainable moving forward, so I decided to switch tracks and go 
entirely with the librarian model of having each module in its own repo, 
and then put only a few items in a central git repo such as the Puppetfile 
and the environment manifests (and maybe not even those, if I could figure 
out how to get Puppet to deploy itself using itself in some klein bottle 
recursive way).

Having said all that:  Now I'm wondering if anyone has seen any "gotchas" 
with using librarian-puppet with Puppet 4?  Or alternatively, if there are 
any "best practices" to follow for librarian-puppet with Puppet 4?  I'm now 
to the point of rebuilding my puppet playground with Puppet 4 and 
librarian-puppet, and don't want to go down any dark alleyways with 
unfortunate consequences at the end if I don't have to.

Thanks in advance,
- Johnson

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/723d867f-ab21-40c0-be5a-547c69ae0962%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to