Infrastructure as Code, 3rd Edition

Chapter 12. Designing Environments

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 12th 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

Clarify why this chapter is needed if the scope of the book is “as code”? I think it’s to do with the term and concept being sometimes fuzzy, as I mention. So I could just point out that question - why is this chapter needed? Also, I think it’s needed because of design questions around composing an environment of infrastructure components. Environments are a high-level design component, that may cross other components in different ways.

Might need make it more clear that the environments I use in examples are not ones I consider to be the only recommended environments. Could list examples of other environments that are often seen?

Should mention local (dev/sandbox/etc.) environments here. Does the stuff in the pipeline chapter 17 belong here?

Generally, need make this chapter and the delivery process flow together more clearly. Reviewers seem to expect this chapter to talk about workflows, ...