On Thu, Feb 24, 2011 at 1:29 PM, Thomas Bellman <[email protected]> wrote: > Stefan Baryakov wrote: > >> Would anyone share workaround for the bug in the subject. >> (http://projects.puppetlabs.com/issues/3910) >> Apologizes if that has been answered, I couldn’t find anything ant >> it’s a real show-stopper for our planning. > > I think not using 'source => "puppet:///..."' references, but instead > using 'content => file(...)' or 'content => template(...)' everywhere, > would do the trick.
Except you end up shipping the file contents *every* time in the catalog. This kind of sucks. > Except if you have custom facts that differ between environments, > or custom type providers that differ between environments. Then > you are screwed. No you're not? If you're using modules properly with environments, the facts/types/providers are all pluginsync'd from the lib/ subdirectory contents of all the modules in your environment. The facts have no bearing on specifying content instead of source. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
