thats correct, foreman will import the facts as soon as they have been
written to the yaml dir (or if you are using store config as soon as they
are written to the db by puppet).

in foreman deployment scenario, the first time puppet runs is only to fetch
the certificates (e.g. in OS post install), so it can work.
but you are correct that this is a limitation if your facts change often.

btw: the same problem exists with normal external nodes which query the
local yaml files :(

Ohad


On Tue, Feb 16, 2010 at 6:22 PM, Nigel Kersten <[email protected]> wrote:

> On Tue, Feb 16, 2010 at 8:19 AM, Ohad Levy <[email protected]> wrote:
> > probably dumb answer - use foreman as it includes the facts already ;)
>
> but if I understand Foreman correctly, it's getting these from the
> cached version server-side right? Either locally or as part of a task
> from other puppet servers?
>
> This means it's not going to have these facts until the client has
> completed at least one puppet run right?
>
>
>
> > feature requests are welcomed
> > cheers,
> > Ohad
> >
> > On Tue, Feb 16, 2010 at 5:51 PM, Nigel Kersten <[email protected]>
> wrote:
> >>
> >> I'm going to ask what might be a dumb question now.
> >>
> >> Why can't we re-order things such that the external node classifier
> >> doesn't simply get a certname as an argument, but instead receives all
> >> the client facts?
> >>
> >> There is an awful lot of logic I would like to remove from my
> >> manifests and push to the external node classifier, and all of this
> >> logic is based upon fact values.
> >>
> >> If we could do this, even if it required that the external node
> >> classifier be written in Ruby and made use of the puppet libraries, it
> >> would significantly improve the functionality of external node
> >> classifiers in my opinion.
> >>
> >> --
> >> 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]<puppet-users%[email protected]>
> .
> >> For more options, visit this group at
> >> http://groups.google.com/group/puppet-users?hl=en.
> >>
> >
> > --
> > 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]<puppet-users%[email protected]>
> .
> > For more options, visit this group at
> > http://groups.google.com/group/puppet-users?hl=en.
> >
>
>
>
> --
> nigel
>
> --
> 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]<puppet-users%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>

-- 
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.

Reply via email to