This seems to use the same Puppet::Module.find function that yours did -
the only difference I can see is that he gets the environment using
compiler.environment.to_s
instead of
Puppet[:environment]
- is that the improved generic part you're referring to?
On Thursday, August 9, 2012 9:50:5
On Thu, Aug 9, 2012 at 1:45 PM, j4m3s wrote:
> I only just noticed this, but I was actually modifying your gist KW to add
> the puppet:/// parsing. I've forked it but can't see how to create a
> pull-request for it (I'm fairly new to gihub I'm afraid).
>
> Anyway, for anyone else wanting the func
I only just noticed this, but I was actually modifying your gist KW to add
the puppet:/// parsing. I've forked it but can't see how to create a
pull-request for it (I'm fairly new to gihub I'm afraid).
Anyway, for anyone else wanting the function I've posted it here:
https://gist.github.com/33
Fantastic thank you Nan, I'll give this a try tonight. It should be easy
to modify yours to do what I need, thank you for sharing it :)
On Tuesday, August 7, 2012 10:52:42 PM UTC+1, Nan Liu wrote:
>
> On Tue, Aug 7, 2012 at 11:13 AM, Krzysztof Wilczynski
> > wrote:
> > Hi James,
> >
> > [...
On Tue, Aug 7, 2012 at 11:13 AM, Krzysztof Wilczynski
wrote:
> Hi James,
>
> [...]
>> How could I acheive this please? I'd rather not hard-code the full path as
>> this would be brittle - how can I "resolve" the puppet:/// url to the actual
>> file location please?
>
> Using "puppet:///" and "f
Hi James,
[...]
> How could I acheive this please? I'd rather not hard-code the full path as
> this would be brittle - how can I "resolve" the puppet:/// url to the actual
> file location please?
Using "puppet:///" and "file:///" in a way similar to what the File type offers
from within a cus
