On Tuesday, March 1, 2016, Matthew Gaspar <gat...@gmail.com> wrote:
> The only problem I sometimes encounter, which may be a usage issue on my
> part, is when creating custom facts sometimes it'd be nice to just run
> `facter my_custom_fact` to get the output. If there would be some way to
> register custom facts so that facter picks them up without having to run
> puppet or run the ruby code the custom fact is in manually, that would be
> interesting. If that already exists I haven't found how to do that.
>
This probably isn't in scope for this, but the above is my most highly
sought after goal.
> Either way, I think a config where you can either specify which facts to
> enable or disable would be useful.
>
We manage firewalls and routers as well as server OSes and it would be nice
to flag which facts shouldn't cause errors on every run on those nodes. I
would suggest this information should be available locally AND/OR through
the master/agent mechanism somehow - please don't require yet another
file{} resource for puppet related settings in every node's manifest.
--
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-eEdup-%3DM2jJH-8-_GFj4EywQjX%2BihaS%2BLhgC8_9di_g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
