On Tue, Jan 18, 2011 at 09:23, windowsrefund <windowsref...@gmail.com> wrote:
> I've got a simple local module that I'll be compiling with the puppet
> binary. The module's structure is:
>
> modules/ub/
> modules/ub/manifests
> modules/ub/manifests/init.pp
> modules/ub/lib
> modules/ub/lib/facter
> modules/ub/lib/facter/factery_import.rb
>
> modules/ub/manifests/init.pp is just a placeholder:
>
> class ub {
> }
>
> My expectation is that I'd be able to run the puppet binary as follows
> and the factery_import.rb script would run
>
> puppet -d --modulepath=modules -e 'include ub'
>
> This does not work though. I can work around it by using export
> FACTERLIB=modules/ub/lib/facter but I'd like to avoid that if at all
> possible. Am I missing something obvious here?
No, that looks like it should work to me. Specifically, by testing
with 2.6.4 shows that it actually works correctly when I run that some
code; puppet loads the fact and I see my debug output showing that it
was found.
Can you post the versions and put the code up to download? If you do
we can try out the system and see if it will reproduce for us locally.
(Knowing exactly what version of puppet you have will also help,
because it will let me test the same code you use rather than just
whatever I have on my system.)
Regards,
Daniel
--
⎋ Puppet Labs Developer – http://puppetlabs.com
✉ Daniel Pittman <dan...@rimspace.net>
✆ Contact me via gtalk, email, or phone: +1 (503) 893-2285
♲ Made with 100 percent post-consumer electrons
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
