I commented on https://github.com/puppetlabs/beaker/issues/499 with my
method for adding a custom (closed sourced; boo) hypervisor for testing in
one module. The exact same mechanism could be used for all manner of
extension gems (or one gem, as beaker-extensions is).
beaker-rspec is essentially a
Hi,
I would be interested to help out here too. We need things like a custom
provider for our own cloudy thing at Spotify and a few other extension
points so that we can move away from rspec-system-puppet .
On Sunday, 30 November 2014 23:54:40 UTC+1, Justin Stoller wrote:
>
> I've been working
I've been working with the module team here and have been looking at
helping out with some of the features we need (pluggable hypervisors,
improved Vagrant support, improved Windows support, better RSpec
formatting...). I was trying to figure what things I'd work on during
#puppethack, but if there
I have to +1 this as well. I think it is hugely important to work out an
extension mechanism if only so that we can eventually break up the codebase and
have them managed separately.
I am pretty familiar with the code at this point so I am happy to get involved,
either directly on the current
I think this is a good idea. It is a bit concerning that Alice doesn't
think there is a good way to add extensions to beaker right now, maybe
development time at #puppethack could be spent shoring that up. I'm +1
on this and would add my limited experience to the maintainer hat pool.
--
Spencer K
Hi All!
So, Beaker is awesome. But there are some features that are nice-to-haves
that aren't needed for Puppetlabs themselves:
https://github.com/puppetlabs/beaker/issues/512
https://github.com/puppetlabs/beaker/issues/499
So, I thought about having these as extensions in a separate gem, that
