A Test Kitchen Driver for Scaleway.
This driver depends on the Scaleway gem. Additionally, you will need to create an account on Scaleway https://www.scaleway.com.
Currently, there is no omnibus package for Test Kitchen to use via this driver. However, as this driver exists I aim to publish some soon.
Please read the Driver usage page for more details.
There are two required options which can either be set as system environment variables or as driver options.
export SCALEWAY_ORG_TOKEN='66c8226d-4b6d-455a-a40a-507faa3fac2b' export SCALEWAY_ACCESS_TOKEN='1800d055-03ef-4109-9ad9-0d3c2cb2004a'
driver: name: scaleway scaleway_org: 66c8226d-4b6d-455a-a40a-507faa3fac2b scaleway_access_token: 1800d055-03ef-4109-9ad9-0d3c2cb2004a
Determines whether or not a Chef Omnibus package will be
installed. In the current state of this project, we recommend setting this
false. We are hard at work to provide an alternate Omnitruck end-point
with Omnibus builds available for all the available flavors, but it is not
available at this time.
There are several different behaviors available:
true- the latest release will be installed. Subsequent converges will skip re-installing if chef is present.
latest- the latest release will be installed. Subsequent converges will always re-install even if chef is present.
10.24.0) - the desired version string will be passed the the install.sh script. Subsequent converges will skip if the installed version and the desired version match.
nil- no chef is installed.
The default value is unset, or
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
Much of this code was derived and borrowed from kitchen-digitalocean.
Apache 2.0 (see LICENSE)