This message was deleted.
# puppet
s
This message was deleted.
c
I see quite a few references
None of the CAT modules use it but it seems to be present in core modules and even the puppet_agent bolt module
b
ah I feared that šŸ˜„
c
ha yeah.. theres bound to be a ton of legacy stuff that has been left because it just works
b
yeah
c
This is going to need coordination between the different teams I think
I’d be looking at the ECOSYSTEM team to work out a plan (i think)
@binford2k @edwin @David Sandilands
What is the upgrade path to beaker_puppet_helpers like?
b
if you only use modules that are defined in your metadata.json you don't need to change anything. We just bumped the
beaker
and
voxpupuli-acceptance
dependency in our Gemfiles
c
ah ok, so potentially an easy transition for the module owners then
b
if you install additional modules; we have a new method to install those: https://github.com/voxpupuli/puppet-nginx/commit/cae3388db238b09374fabfe3d49d1fdf42882120
I think out of ~190 modules we had to update ~30 with a 2-3 line patch
c
šŸ‘
thanks for the additional info
b
when you have a lot of modules in metadata.json you will have a significat performance boost with the new gem
because it doesn't use
puppet module install $module
for each module anymore
I also want to advocate for https://github.com/voxpupuli/voxpupuli-acceptance , which abstracts most of the beaker bits away and also makes the beaker 4->5 migration easy. We use that on all modules and at a few customers
c
yeah for sure
i think this is a good choice for those that are using beaker internally
šŸ‘ 1
b
if anyone has questions about it, jsut redirect them to me