Not a bad idea, thanks for the suggestion!
On Monday, September 17, 2012 2:39:15 AM UTC-7, Stefan Goethals wrote:
>
> Why not simply puppetdb::server for the ... well, puppetdb server and
> puppetdb::client for... the client, as that is exactly what the
> puppetmaster is to puppetdb?
>
> Regards
That's a fair statement; it's been brought up around the office. The goal
for now is to have a single puppetdb module that is capable of managing
everything related to puppetdb, and then potentially later wrap some subset
of the puppetdb classes in the puppet/master module. For the short term,
Why not simply puppetdb::server for the ... well, puppetdb server and
puppetdb::client for... the client, as that is exactly what the
puppetmaster is to puppetdb?
Regards,
Stefan.
On Sat, Sep 15, 2012 at 4:03 PM, Ashley Penney wrote:
> I kind of feel like the reason you're having a problem nam
I kind of feel like the reason you're having a problem naming this is
that it doesn't really belong in the puppetdb class but in the puppet
module that sets up the server. :)
That's how I did this, I have a puppetdb module that purely sets up
puppetdb and then puppet::server::puppetdb to handle th
Anyone interested in helping me name a class in the forthcoming puppetdb
module?
There are 2 major parts to the module... the part that sets up puppetdb
itself, and the part that sets up the puppet master to talk to puppetdb.
I'm brainstorming names for the latter... a class that you would apply
