A Test Kitchen Driver for Debian.
TODO: document any software or library prerequisites that are required to
use this driver. Implement the #verify_dependencies method in your Driver
class to enforce these requirements in code, if possible.
- Download a Debian install medium and start it
- Hit escape key
- Type install auto=true priority=critical preseed/url=https://raw.githubusercontent.com/bob5ec/kitchen-debian/master/preseed Please read the Driver usage page for more details.
- deploy vault docker image somewhere
- create deploy script to register new debian installation within vault create ssh key and put IP along with private key into vault
- create kitchen.io plugin to provide newly created installation to kitchen
- german keyboard
- upgrade packages
- set mirror
TODO: Write descriptions of all configuration options
Determines whether or not a Chef Omnibus package will be installed. 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.<VERSION_STRING>(ex: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.falseornil- no chef is installed.
The default value is unset, or nil.
- 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 and maintained by bob5ec (bob5ec@users.noreply.github.com)
Apache 2.0 (see LICENSE)