I'd like to add that *IF* you are using Foreman as an ENC, the
preferred method of putting facts in the Foreman database is the new
ENC script that updates facts on every puppet run:
https://github.com/theforeman/puppet-foreman/blob/master/templates/external_node.rb.erb
Where you might want to use storeconfigs, is if you want to use the
Puppet language's storeconfig syntax to export and collect resources.
(Or have existing code that uses storeconfigs syntax). You do NOT need
to share the database to do this, and in fact I am personally
discouraging a shared database, since Puppetlabs has indicated that
they eventually plan to deprecate mysql based storeconfigs, and using
UUID certnames in conjunction with Foreman provisioning doesn't work
with a shared database.
While we now have separated our storeconfigs database from the foreman
database, and still have code that uses storeconfigs operators, I am
exploring replacing our storeconfigs code with native puppet functions
that work with foreman searches, as described here:
http://blog.theforeman.org/2012/01/getting-foreman-search-results-into.html
We can do this because we are using the ENC script to keep facts up to date.
I'd love to hear other people's thoughts on this.
Cheers,
Brian
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To view this discussion on the web visit
>
https://groups.google.com/d/msg/puppet-users/-/rfP-dJMulcgJ.
>
> To post to this group, send email to
puppet...@googlegroups.com.
> To unsubscribe from this group, send email to
>
puppet-users...@googlegroups.com.
> For more options, visit this group at
>
http://groups.google.com/group/puppet-users?hl=en.