On Fri, May 14, 2010 at 1:42 PM, Paul Lathrop <[email protected]>wrote:
> >>> Assuming the client has puppeted at least once against that server. > This > >>> won't work for bootstrapping a client though will it? > >> > >> it does, the facts yaml file is created before the external node > >> classifier is called ;) > > > > Whoa. This should be called out in the external node docs, as I simply > > assumed this happened after the node classifier is called. > > +1000 > > I did some tests as I didn't quite trust this :) and it's absolutely true. So my plan is for my external node provider to redirect clients that haven't provided facts to a "bootstrap" environment that contains the bare minimum facts that are required to work out what environment they should be in, and then my puppetd wrapper scripts to detect that a bootstrap run has occurred (probably a file set to be present on the bootstrap run and absent on all other runs) and re-run. How could we achieve the same functionality within puppetd itself? I can't think of a way this could be done right now with it running as a daemon. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
