version control

A system, usually Git, that records every change to a set of files with who made it and why, so work can be reviewed and rolled back.

In more detail

Instead of copies named final and final-v2, a version control system keeps each version of the whole project together with its author, time and message. It lets several people change the same files, review each change and roll back mistakes. Git is by far the most common one.

Examples

Playbooks, inventories, roles and Vault-encrypted files belong in version control; vault passwords never do.
In Git, each saved version is a commit, and git log lists them.
The course keeps policies, lockfiles and baselines in version control so every change to them has an author and a reviewer.
In Terraform: Git is the version control system almost every team uses. Infrastructure as code depends on it: configuration, the dependency lock file and variable files are committed, while the .terraform directory and state files are not. Every change to infrastructure then has a history and can go through review.

Related terms

Taught in

References

Certification courses