The DevOps Handbook: How to Create World-Class Agility, Reliability, & Security in Technology Organizations

by Gene Kim

To ensure that we can restore production service repeatedly and predictably (and, ideally, quickly) even when catastrophic events occur, we must check in the following assets to our shared version control repository: •all application code and dependencies (e.g., libraries, static content, etc.) •any script used to create database schemas, application reference data, etc. •all the environment creation tools and artifacts described in the previous step (e.g., VMware or AMI images, Puppet, Chef, or Ansible scripts.) •any file used to create containers (e.g., Docker, Rocket, or Kubernetes definitions or composition files) •all supporting automated tests and any manual test scripts •any script that supports code packaging, deployment, database migration, and environment provisioning •all project artifacts (e.g., requirements documentation, deployment procedures, release notes, etc.) •all cloud configuration files (e.g., AWS Cloudformation templates, Microsoft Azure Stack DSC files, OpenStack HEAT) •any other script or configuration information required to create infrastructure that supports multiple services (e.g., enterprise service buses, database management systems, DNS zone files, configuration rules for firewalls, and other networking devices)