A Test Kitchen Driver for Blue Box Blocks.
This driver uses the fog gem to provision and destroy blocks instances. Use Blue Box's cloud for your infrastructure testing!
There are no external system requirements for this driver. However you will need access to a Blue Box account.
Please read the Driver usage page for more details.
Required The Blue Blue customer id to use.
The default is unset, or nil
.
Required The Blue Blue api key to use.
The default is unset, or nil
.
The blocks product type (also known as size) to use.
The default is "94fd37a7-2606-47f7-84d5-9000deda52ae"
.
The blocks template id to use.
The default is "573b8e80-823f-4100-bc2c-51b7c60f633c"
.
The blocks location to use.
The default is "37c2bd9a-3e81-46c9-b6e2-db44a25cc675"
.
The SSH port number to be used when communicating with the instance.
The default is 22
.
Path to the private SSH key used to connect to the instance.
The default is unset, or nil
.
The SSH username that will be used to communicate with the instance.
The default is "kitchen"
.
The following could be used in a .kitchen.yml
or in a .kitchen.local.yml
to override default configuration.
---
driver:
name: bluebox
bluebox_customer_id: 123...
bluebox_api_key: abc...
location_id: def789...
ssh_public_key: /path/to/id_dsa.pub
ssh_key: /path/to/id_dsa
platforms:
- name: ubuntu-12.04
driver:
image_id: b137c423-bade-4b01-9d13-271eea552563
- name: scientific-6.3
driver:
image_id: caaaca6b-fbe0-4e27-af2b-d100e46767bd
suites:
- name: default
Both .kitchen.yml
and .kitchen.local.yml
files are pre-processed through
ERB which can help to factor out secrets and credentials. For example:
---
driver:
name: bluebox
bluebox_customer_id: <%= ENV['BLUEBOX_CUSTOMER_ID'] %>
bluebox_api_key: <%= ENV['BLUEBOX_API_KEY'] %>
ssh_public_key: <%= File.expand_path('~/.ssh/id_dsa.pub') %>
ssh_key: <%= File.expand_path('~/.ssh/id_dsa') %>
platforms:
- name: ubuntu-12.04
driver:
image_id: b137c423-bade-4b01-9d13-271eea552563
- name: scientific-6.3
driver:
image_id: caaaca6b-fbe0-4e27-af2b-d100e46767bd
suites:
- name: default
- Source hosted at GitHub
- Report issues/questions/feature requests on GitHub Issues
Pull requests are very welcome! Make sure your patches are well tested. Ideally create a topic branch for every separate change you make. For example:
- Fork the repo
- Create your feature branch (
git checkout -b my-new-feature
) - Commit your changes (
git commit -am 'Added some feature'
) - Push to the branch (
git push origin my-new-feature
) - Create new Pull Request
Created by Fletcher Nichol (fnichol@nichol.ca) and maintained by Blue Box Group
Apache 2.0 (see LICENSE)