Re: [Puppet Users] Force Fact within manifest

Personally, I've never come across a case where I needed a post-mortem fact collection. But, I do tend to write custom types when I need to get things into the catalog so that may be my particular way of doing things coming out. While this could be useful in some cases for reporting, I would very

Re: [Puppet Users] Force Fact within manifest

I like the idea. Personally I've always wished to just see facts in the form of: pre_puppet => post_puppet You now have a record of what it was before going into puppet as well as a record when it comes out. Thats about the best accuracy one can hope for. -- You received this message

Re: [Puppet Users] Force Fact within manifest

On Tue, Mar 1, 2016 at 9:09 AM, JS wrote: > Which guy? The OP? > > Yep, OP, per the rest of the post. > > That's not what anyone else in this necro'd thread said back in its >> previous life, so exactly what and who are you agreeing with? > > Yes, it was actually this

Re: [Puppet Users] Force Fact within manifest

> > Which guy? The OP? Yep, OP, per the rest of the post. That's not what anyone else in this necro'd thread said back in its > previous life, so exactly what and who are you agreeing with? Yes, it was actually this necro'd threads main point of emphasis, including subject, introduction,

Re: [Puppet Users] Force Fact within manifest

On Monday, February 29, 2016 at 1:24:44 PM UTC-6, JS wrote: > > Im going to second this guy. > Which guy? The OP? > I believe puppet should ALWAYS collect facts after it is done. > That's not what anyone else in this necro'd thread said back in its previous life, so exactly what and

Re: [Puppet Users] Force Fact within manifest

Im going to second this guy. I believe puppet should ALWAYS collect facts after it is done. The amount of changes it can make to a server, during a catalog run, can be massive. Without reporting those changes, bad things can occur. It really really limits the potential of having a complete

Re: [Puppet Users] Force Fact within manifest

On Tuesday, October 8, 2013 6:08:56 PM UTC-5, Paul Oyston wrote: I'm really only wanting an up to date set of facts once the puppet agent has finished making changes to the system, I'm not wanting to modify the catalog run process by modifying facter values during the run process. I'm

Re: [Puppet Users] Force Fact within manifest

Hi Wolf, Thanks for that diagram, that's incredibly helpful. It seems a bit of an oversight not to allow facts to be updated during the manifest phase since manifests are making changes to the system and therefore potentially modifying facts during their run. I might look into modifying the

Re: [Puppet Users] Force Fact within manifest

For anyone else wanting to do something similar: For now I've just used the postrun_command on the puppet agents so that the facts will be uploaded to the server once modifications have been made. e.g. postrun_command puppet facts upload This will then re-upload the facts once the puppet agent

Re: [Puppet Users] Force Fact within manifest

I'm really only wanting an up to date set of facts once the puppet agent has finished making changes to the system, I'm not wanting to modify the catalog run process by modifying facter values during the run process. I'm aware that the facts are evaluated and the manifests compiled at the

[Puppet Users] Force Fact within manifest

I have a requirement where I want a Fact to be stored in PuppetDB during the manifest run and not during the initial fact gathering phase. I know I can, in my manifests, create a file in /etc/facter/facts.d or I can write a Ruby script that will then be distributed by plugin sync. But both of

Re: [Puppet Users] Force Fact within manifest

Hi Paul, Here's a diagram showing how the puppet run process flows: http://www.aosabook.org/images/puppet/TimingDiagram.png as you can see, facter is run exactly once, before the catalog is created. facter is not invoked again until the next run. I suppose you could have your sshkey resource