I am using this in a puppet post run command to upload the facts that changed after the puppet run.
I have run into this problem on many occasions where I like to build a custom UI around displaying custom facts. Because facts only get uploaded to puppetdb before the puppet agent runs so there has always been a delay of one puppet run in realizing what the environment actually looks like. So to fix this we used the puppet facts upload functionality. There are many custom facts that interact with the software that puppet was deploying. So in a way we are using facts outside of puppet but we are using puppetdb's REST API to retrieve those facts and display to our developers. Basically we use facts as infrastructure metadata that we can display to our developers and devops team to make informed decisions about what's deployed where and who broke the environment by showing latest git revisions of the deployed code. If you would like to talk further about this please reach out to me via email. Corey On Thursday, October 2, 2014 1:55:11 AM UTC-7, Ken Barber wrote: > > > We do this, but could probably live without it. But we do it using the > facts > > indirector and setting it up to cache to puppetdb. > > So in both cases you use 'puppet facts upload'? > > ken. > -- 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/65cdb9cb-197d-4fa5-aff4-c0832cd8485a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
