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 if you have custom facts that differ between environments,
or custom type providers that differ between environments. Then
you are screwed.
/Bellman
--
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.