That's fine.
Can you put your code into PasteBin or gist.github.com? We can work from
there.
Cheers,
Felix
On 11/19/2013 05:06 PM, ulrich igor ngouagna kouete wrote:
> Sorry but I do not understand :( I'm quite a newbee in all these...
--
You received this message because you are subscribed to
Sorry but I do not understand :( I'm quite a newbee in all these..
Le mardi 19 novembre 2013 15:45:06 UTC+1, Felix.Frank a écrit :
>
> Hi,
>
> where does the ruby code of your custom type reside?
>
> Make sure that ruby's include path (`ruby -e 'puts $:`) will read your
> working tree first. To
Sorry but I do not understand :( I'm quite a newbee in all these...
Le mardi 19 novembre 2013 15:45:06 UTC+1, Felix.Frank a écrit :
>
> Hi,
>
> where does the ruby code of your custom type reside?
>
> Make sure that ruby's include path (`ruby -e 'puts $:`) will read your
> working tree first. T
Hi,
where does the ruby code of your custom type reside?
Make sure that ruby's include path (`ruby -e 'puts $:`) will read your
working tree first. To be safe, run puppet as
RUBYLIB=/path/to/my/lib puppet apply .pp
HTH,
Felix
On 11/19/2013 12:25 PM, ulrich igor ngouagna kouete wrote:
> Hi,
>
Hi,
I'm trying to develop a custom type, and I'm working on a stand alone mode
(using puppet apply to apply my manifest). After modifying the type (adding
a new parameter for example), when I try to apply the manifest again, it
says that the new param is unknown. I found on the official doc tha
