The Continuous Delivery Pipeline is familiar to most developers. It’s a collaborative process built upon loops of feedback at every stage. A new feature will defined between a Product Manager, a Developer and a Quality Analyst. A pair of Developers will work together on the implementation following a Test Driven Development approach using the tests as feedback to guide progress. The new code is compiled with the master branch and all of the unit tests are run. The application may be deployed to a test environment and a series of Acceptance Tests will be run. All of this feedback gives the confidence to proceed to a Production deployment at which point Ops take over and the developers pick up a new change.
This is wrong. The Developers’ involvement stops too soon. The change is thrown over the wall to another team and the feedback cycles stop.
Information visualisation is used for visually representing data to reinforce and enhance cognition. When deploying infrastructure as code, this visual perspective of resources and their relationships can prove useful, both at the design stage, and also post deployment for purposes of troubleshooting and infrastructure development. In this post we take a look at how to achieve visual outputs for Terraform plans using auto-generation.Continue reading “Auto-generated infrastructure node graphs from Terraform plans”
DevOpsDays was back in London this week and was lucky enough to go along on the second day. The format was a mix of presentations the morning, ignite talks after lunch and Open Spaces for the remainder of the day. I particularly like this mix as the talks give context and knowledge sharing in a structured way whilst the open spaces give the opportunity to talk with your peers.