Hi,
Adding reusable Chef steps to Cuken is progressing.
At the moment I’m assuming you point to a Chef server (i.e. I don’t
mock the Chef server per the upstream-Chef features).
It turns out Aruba covers much of the use case, with some convenience
steps when some configuration is required.
Knife could help in the future by warning about invalid options
instead of exiting - at the moment it looks like we’ll have to
reproduce some of knife’s options logic,
e.g you can’t pass a cookbook path to all subcommands - some will
refuse to continue even though it is an irrelevant option.
Finally, while I’m working off the upstream-Chef steps, do people have
common steps they are tired of defining, which care to throw out here.
Example:
I interactively run Knife’s “([^”]*)"
- sets stored cookbook and config paths
TIA
–
πόλλ’ οἶδ ἀλώπηξ, ἀλλ’ ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com