Cuken's first minimally-functional release: 0.1.13


It is not the most glamorous task, but cuken0, as of v 0.1.13, is
getting close to being useful.
Specifically, read the about cuken1, makes some changes to the Zenoss example:

  • Change the couple of Github writable URI’s
  • Point to your Vagrant basebox

Then execute the Zenoss example features: one2, two3, three4. Done.

This is still version 0.1.13, but from here on hopefully basic
functionality won’t break, but don’t
be surprised if step definitions change rapidly.
Which is where you come in… any bug reports, suggestions for better
(succinct) steps, or new steps are welcome.
Most welcome are API specs.
Don’t spam the list, rather issue a pull request or open an issue on Github.

Interactive SSH steps have been of some use to me (e.g. fixing the
file permissions issue in Chef 0.10.0.rc.2), at the moment they just
work to Vagrant VM machines. Since this is my immediate need they are
likely to fall down the to do list.
However, generic interactive SSH steps may what you want, right-now.
If so all the necessary code is in the SSH API files, the API+steps
just need to be touched up. If this is a urgent itch for you, take a
look at the features files in SSH-Forever for a very rough first draft
of what is possible. Essentially I just pulled all my SSH-Forever code
changes into cuken.
One critical point - no SSH passwords. None. Only key based
connections in cuken.

Again, as you’d expect with 0.x versions, this is very raw, and may
change rapidly from time to time, so be prepared to periodically
rework your feature files (for the better) until the 1.0 release.
I’ve been running this with Chef 0.10.rc.2, so the 0.10.0 release
should be no worse.

Best wishes

πόλλ’ οἶδ ἀλώπηξ, ἀλλ’ ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)