This is pretty killer. We use Chef, and although its repeatable results are nice, coding for chef and deploying via knife seems tougher than it needs to be.
This seems to have serious potential to position chef as a way of communicating configuration while requiring very little direct writing of code for Chef.
Definitely. We want people sharing their configs more, just like code. Secondly, we feel that for most people, configuring via the command-line is more natural, or at the very least an easier way to get started w/ puppet or chef.
Exactly this. Getting a config running is quite often an iterative and exploratory process that should not be enshrined in structure until it's actually running. You get this, which is why Blueprint makes sense.
Comments
This is pretty killer. We use Chef, and although its repeatable results are nice, coding for chef and deploying via knife seems tougher than it needs to be.
This seems to have serious potential to position chef as a way of communicating configuration while requiring very little direct writing of code for Chef.
Definitely. We want people sharing their configs more, just like code. Secondly, we feel that for most people, configuring via the command-line is more natural, or at the very least an easier way to get started w/ puppet or chef.
Exactly this. Getting a config running is quite often an iterative and exploratory process that should not be enshrined in structure until it's actually running. You get this, which is why Blueprint makes sense.