Create a `librarian-provisioner` gem that both `librarian-chef` and `librarian-puppet` can use

[patcon]

Not sure how realistic this is, but wanted to start a stub for discussion. ~~Just noticing that librarian-chef and librarian-puppet are starting to diverge a bit in functionality, but seems that many features could be shared between each.~~ Sorry, not really true.

If nothing else, an abstracted gem might provide a shared turf to discuss new features that might equally benefit the other community :)

Not entirely sure whether this is a good idea, but just tossing it out there!

cc: @yfeldblum @benburkert @rodjek

EDIT: Another bonus is that it might be much, much simpler for other config management communities to maintain their own tools:

• Salt: https://github.com/sveinung/librarian-salt cc: @sveinung
• Ansible: ?
• Cfengine: ?
• ???

[paulruiz]

There is an abstract gem: librarian. This recently was split off from librarian-chef which is what libararian-puppet vendors

[patcon]

Thanks @paulruiz, but I'm aware of the librarian gem. I'm just looking librarian-puppet and librarian-chef and seeing lots of common ground, so I'm wondering how the maintainers feel about sharing more code. I tend to float ideas before spending too much time on them, in case they turn out to be ideas that people are specifically against implementing