On Tuesday, March 1, 2016, Kylo Ginsberg <k...@puppetlabs.com> wrote: > > Does 'facter -p my_custom_fact' do the trick here? >
In my case, it's while developing the fact, prior to distribution. Takes some trickery to rig it up for testing. > Ah yeah, I've heard this a few times as well. But why is it more of a > thing on firewalls/routers? > Lots of the binaries and even paths don't exist, so some of the common facts spew errors; anything custom and you have to deal with the errors in your logs or your two liner becomes an excessively defensive novel. > Is the concern here about manifest bloat? > Some. It also separates apply and agent, which may have different desires. On the agent, I may want something different for production vs a feature branch, too, where the fact may actually be in development. If that could be done via environment.conf, say, it could help. -- Rob Nelson rnels...@gmail.com -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CAC76iT_TuDGkebhL_%3DjrB9%3DOCZr2M4_tjF77nZFoj6Qao8GbLQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
