On Wednesday, December 19, 2012 1:02:48 PM UTC-8, Ramin K wrote: > > On 12/19/2012 11:55 AM, David Kerr wrote: > > Howdy, > > > > I've got a module that's the equivalent of: > > /etc/puppet/modules/mymodule/lib/facter/myfact.rb > > > > myfact.rb seems to get pushed to all nodes regardless of whether or not > > i include mymodule for that node. > > > > my factpath is > > factpath = $vardir/lib/facter:$vardir/facts > > > > I'm on puppet v 3.0.0 > > > > I'm fairly certain that my site manifests are correct, so I don't > > believe that this node is falling through and hitting a different node's > > set of includes. > > > > It's unclear if this is the expected and correct behavior for puppet? > > > > Thanks > > This is the correct behavior and makes sense if you think about > the > order of transactions. > > 1. client connects to master and does cert things > 2. master sends facts to client > 3. client runs facts, POST to master requesting catalog > 4. master generates catalog based on facts > 5. client receives catalog and executes it > > Because facts are run before the catalog is requested they can't be > doled out on demand. > > Ramin >
good to know, thanks! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/bYteczZEQ18J. 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.
