Follow me on Twitter @deanbryen for new posts and I'd also love to hear your thoughts and feedback.
I bumped into an old friend on the train the other day and after we’d got through the usual small talk of asking how each others kids were getting on, we got into the exciting topic of infrastructure automation. Particularly Infrastructure as Code (IaC), the process of treating our infrastructure in the same way we would treat our code. Something he was looking to implement within his own organisation. During that conversation My friend said something that would stick on my mind for the rest of the day, and is the inspiration for this blog series:
‘It’s ok creating a Terraform template, but my team don’t understand git workflow, or how to build, test and release these through a ci/cd pipeline’
He was 100% right. Most people looking after infrastructure deployments in organisations aren’t software developers, they’ve maybe never used git, or created a build pipeline, and maybe never wrote a line of JSON or YAML. Infrastructure as code is so much more than just writing a JSON template anyway!!
During this upcoming blog series, I’ll be covering all aspects of Infrastructure as Code, from End to End. The concepts you’ll learn can be transferred to any cloud provider or IaC provider, but we’ll be working mainly with Azure and Terraform for the demos here. It’ll look a little something like this and I’ll be releasing one post a week:
Part 1 - Defining our infrastructure as templates
Part 2 - Putting our templates in Source Control
Part 3 - CI/CD - Creating an infrastructure pipeline (build and test)
Part 4 - CI/CD continued (deployment)
Part 5 - Infrastructure Template Design Patterns
Remember, it’s not about ‘
defining our infrastructure as code’ it’s about ‘TREATING our infrastructure as code’ and there’s so much more to that than a simple JSON template.
I’ll see you in the next post!