puppet support probably was missing because it's quite tricky to implement.
Since I've started looking into writing my own functions and modules and
get a bit deeper into puppet I might actually look into this myself if I
find the time. If I make any progress there you can expect a pull request
for the changes :)
On Monday, April 23, 2012 3:57:08 PM UTC+2, matti wrote:
Hi,
Apologies for that :-(
Adding support for "puppet://" is quite tricky (there is a lot going on
under-the-hood with this one), and I never have the time to do it (unless
somebody is willing to help out and/or sponsor).
For the time being, please bare with fully-qualified paths ...
KW
--Hi,
On Monday, 23 April 2012 13:59:00 UTC+1, Dennis Jacobfeuerborn wrote:
Thanks, this looks like it will do the trick. The lack of puppet://
support probably means I will have to hard-code a path to a directory
somewhere but that shouldn't be to big of a deal.
[...]Thanks, this looks like it will do the trick. The lack of puppet://
support probably means I will have to hard-code a path to a directory
somewhere but that shouldn't be to big of a deal.
Apologies for that :-(
Adding support for "puppet://" is quite tricky (there is a lot going on
under-the-hood with this one), and I never have the time to do it (unless
somebody is willing to help out and/or sponsor).
For the time being, please bare with fully-qualified paths ...
KW
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/NAMjjrnooXwJ.
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.
