----- Original Message ----- > From: "Henrik Lindberg" <henrik.lindb...@cloudsmith.com> > To: "puppet-users" <puppet-users@googlegroups.com> > Sent: Saturday, November 21, 2015 4:08:00 PM > Subject: Re: [Puppet Users] Re: puppet lookup in an apply settings
> On 2015-20-11 13:00, R.I.Pienaar wrote: >> It works in the basic sense, but does not appear in my case to have >> access to the node facts (ie. the node its being run on), particularly >> fqdn etc, so the node specific tier isnt loaded. >> >> > > There are a couple of bugs reported regarding --node and --facts and the > lookup application. Our testing has primarily been master side, but > command should also work for masterless configuration - please report > issues in Jira if you find something not already reported. OK, will do was just checking if it was intended to work. I am working on a few bugs that I found, one is proving to be very hard to even reproduce in a simple case. 2 modules, if I include module 2 directly it works and does merges as per the lookup_options but if module 1 includes module 2 it does not. So far only happens with one complex code base, not been able to come up with a test case to make a proper bug report :( But the module data and lookup options are really good additions thanks for that -- 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/945327359.2814528.1448122972741.JavaMail.zimbra%40devco.net. For more options, visit https://groups.google.com/d/optout.
