beaker-aws
Beaker library to use aws hypervisor
How to use this wizardry
This gem that allows you to use hosts with aws hypervisor with beaker. Please check out our aws and ec2 docs.
Beaker will automatically load the appropriate hypervisors for any given hosts file, so as long as your project dependencies are satisfied there's nothing else to do. No need to require
this library in your tests.
With Beaker 3.x
This library is included as a dependency of Beaker 3.x versions, so there's nothing to do.
With Beaker 4.x
As of Beaker 4.0, all hypervisor and DSL extension libraries have been removed and are no longer dependencies. In order to use a specific hypervisor or DSL extension library in your project, you will need to include them alongside Beaker in your Gemfile or project.gemspec. E.g.
# Gemfile
gem 'beaker', '~>4.0'
gem 'beaker-aws'
# project.gemspec
s.add_runtime_dependency 'beaker', '~>4.0'
s.add_runtime_dependency 'beaker-aws'
Spec tests
Spec test live under the spec
folder. There are the default rake task and therefore can run with a simple command:
bundle exec rake test:spec
Acceptance tests
We run beaker's base acceptance tests with this library to see if the hypervisor is working with beaker. There is a simple rake task to invoke acceptance test for the library:
bundle exec rake test:acceptance
Transfer Notice
This plugin was originally authored by Puppet Inc. The maintainer preferred that Puppet Community take ownership of the module for future improvement and maintenance. Existing pull requests and issues were transferred over, please fork and continue to contribute here.
Previously: https://github.com/puppetlabs/beaker
License
This gem is licensed under the Apache-2 license.
Release information
To make a new release, please do:
- update the version in
lib/beaker-aws/version.rb
- Install gems with
bundle install --with release --path .vendor
- generate the changelog with
bundle exec rake changelog
- Check if the new version matches the closed issues/PRs in the changelog
- Create a PR with it
- After it got merged, push a tag. GitHub actions will do the actual release to rubygems and GitHub Packages