Hi all,

I tested ib master / agent environment and the problem isn't there 
anymore?! I don't know what went wrong for the first time. But now every 
works as expected. 

Regards
Andreas

Am Montag, 1. Juni 2015 09:30:37 UTC+2 schrieb ashe...@gmail.com:
>
> Hi all,
>
> first thanks to all of you. At least I found a solution taking a bit from 
> all the hints. This is ( one possible ) solution:
>
> irb(main):001:0> require 'facter'
> => true
> irb(main):002:0> require 'puppet'
> => true
> irb(main):003:0> a = Facter.value(:userblweb)
> => nil
> irb(main):004:0> Puppet.initialize_settings
> => "notice"
> irb(main):005:0> a = Facter.value(:userblweb)
> => "1000\n"
>
> As you can see, after invoking initialize_settings my custom fact seems to 
> be in place / known to facter. Now I'll have a look how it works outside 
> irb in real puppet master/agent environment.
>
> Regards
> Andreas
>
> Am Mittwoch, 27. Mai 2015 08:36:39 UTC+2 schrieb ashe...@gmail.com:
>>
>> Hi,
>>
>> is it possible to use custom facts inside other custom facts? 
>>
>> With facter -p the custom fact is listed ( e.g.):
>>
>> ...
>> userblweb => 1000
>>
>> With irb:
>>
>> irb(main):001:0> require 'facter'
>> => true
>> irb(main):002:0> a = Facter.value(:userblweb)
>> => nil
>>
>> Any idea?
>>
>> puppetversion: 3.7.3
>> facter 2.3.0
>>
>> Regards
>> Andreas
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/a6eecf57-1a0a-49af-bdfd-7e073e9c1901%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to