Dustin Collins

[...] of the parser out to create_parser. I did this to make it easier to test. Here are a couple unit tests: tests/test_ping.py In the above test file I set up a CommandLineTestCase class that will add [...]

[...] Chef recipes is a very good idea, but will only get you so far. You can have 100s of passing unit tests and your Chef converges will still fail. Integration testing can greatly increase the [...]

[...] instances. But what happens when you need those keys? I ran across this problem running unit tests on Jenkins for a Chef cookbook that uses citadel to pull config secrets out of S3. I [...]

[...] JSON file CloudFormation needs. A teammate pushes a new feature for the Flask app to Github. A Jenkins job is triggered and runs the tests and linting for the app. If the build is successful, a job is [...]

[...] our tests. Great, now our tests pass and we didn’t have to hard-code any credentials into the Jenkins job! If you’re using boto for Python or fog for Ruby, they will internally query the instance [...]

[...] so far. You can have 100s of passing unit tests and your Chef converges will still fail. Integration testing can greatly increase the confidence you have in your Chef code. In this post, I’ll [...]

[...] for the cookbook On successful build, it triggers a job to push the updated cookbook to the Chef server. We’re using hosted Chef, so we assumed this would be seamless. Nope. A developer would push, [...]

[...] to present information on various subsystems. PyChef A Python API for interacting with your Chef server. I use this in our deployment and monitoring tooling. When I want to deploy an app, I use [...]

Most resources discussing testing with Chef deal with unit testing. Unit testing your Chef recipes is a very good idea, but will only get you so far. [...]

I’m doing a presentation on how to use serverspec to create a tight feedback loop for infrastructure coding at the next Boston DevOps meetup Nov 19t [...]