Feature #347

Cache generated external nodes yaml

Added by Paul Kelly about 9 years ago. Updated about 8 years ago.

Target version:
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:


To increase resilience the externalnodes function should cache its results between runs and if it is unable to generate a new result then it should return the cached value.

This may not be as useful as it seems because the puppet clients will also run the last valid manifest they received. I know that this is not quite the same but it is quite similar.

Associated revisions

Revision 7cfd7544 (diff)
Added by Ohad Levy about 8 years ago

fixes #347 - Cache generated external nodes yaml

this provides saves by default the yaml output from foreman on your

it will default to /var/lib/puppet/foreman directory.

in case of failure/timeout/no reply, it would use the cached version of
the external nodes output.

it also contain the push facts alternative, of pushing a node facts
prior to requesting its external node data.
this is probably the best way to esnure that your foreman instance is
updated while not sending old facts to your foreman server.


#1 Updated by Ohad Levy almost 9 years ago

  • Target version set to 0.2

#2 Updated by Ohad Levy almost 9 years ago

  • Assignee deleted (Ohad Levy)

#4 Updated by Ohad Levy over 8 years ago

  • Assignee set to Paul Kelly
  • Target version deleted (0.2)

#5 Updated by Ohad Levy about 8 years ago

this is mostly done already at

maybe the caching part is worth merging back into foreman puppet module.

#6 Updated by Ohad Levy about 8 years ago

  • Project changed from Foreman to Installer
  • Category deleted (External Nodes)
  • Assignee changed from Paul Kelly to Ohad Levy

#7 Updated by Ohad Levy about 8 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Applied in changeset commit:"7a092772ee8f0f7aeebe2653b3d49135e3035a86".

Also available in: Atom PDF