Infrastructure as Code, 3rd Edition

Chapter 17. Developing and Building Infrastructure Code

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles. This will be the 17th chapter of the final book. Please note that the GitHub repo will be made active later on. If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the editor at [e-mail].

TODO

Look at mentioning dagger.io, earthly.dev, https://github.com/moby/buildkit

The last chapter described using automated pipelines to implement workflows for delivering infrastructure code changes. This chapter focuses on the start of the workflow. Infrastructure developers check out and work on a personal copy of the codebase, then commit their changes to trigger the build stage of the pipeline. The build stage prepares the code for distribution across the rest of the pipeline and into production environments.

The key topics in this chapter are techniques for testing infrastructure code when working on it, approaches for distributing infrastructure code across environments, building code to prepare it for distribution, and strategies for organizing an infrastructure codebase.

Working on Code Locally

The infrastructure delivery workflow starts with an infrastructure ...