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
- Ansible Vault — Ansible's built-in feature and command for encrypting secrets such as passwords and keys so the encrypted files can live in the project.
- secret — Any value that grants access, such as a password, access token or private key, and must be kept out of code and version control.
- Git — A free, open-source distributed version control system that records the history of a project as a chain of snapshots.
- commit — A saved snapshot of the whole project in Git, together with its author, committer, time, message and a pointer to the commit before it.
- codebase — All the source code for a piece of software, usually kept in one or more version control repositories.
- repository — A project folder whose full history is tracked by version control; in Git, your files plus the hidden .git directory that stores every commit.
- centralized version control — A style of version control where one central server holds the only full history and every user works from it.
- distributed version control — A style of version control where every copy of a project carries the complete history, so most work needs no server.
- pull request — A request on a hosting service such as GitHub to merge one branch into another, with a page for review, discussion and automated checks.
Taught in
- What Configuration Management Is — Ansible Configuration Management at Scale
- Securing Data With Ansible Vault — Ansible Configuration Management at Scale
- Security Baselines, Policies & Hardening Standards — Cybersecurity Fundamentals, GRC & Cryptography
- Throughput: Change Lead Time And Deployment Frequency — DevOps & Site Reliability Engineering
- Codebase And Dependencies — DevOps & Site Reliability Engineering
- Why Version Control, And Why Git Won — Advanced Git Internals & Distributed Workflows
- What A Commit Really Is — Advanced Git Internals & Distributed Workflows
- Editors, IDEs And Shells — Hands-on Python: Complete Video Course & Book
- Virtual Environments — Hands-on Python: Complete Video Course & Book
- Workload Identity — Application Security & Threat Modeling for Engineers
- Dependency Risk And Typosquatting — Application Security & Threat Modeling for Engineers
- What Is Infrastructure As Code? — Infrastructure as Code with Terraform
- Initialising The Working Directory — Infrastructure as Code with Terraform
- Parameterising With Input Variables — Infrastructure as Code with Terraform
- Infrastructure As Code, And One Workflow For Every Platform — HashiCorp Terraform Associate (004) Exam Prep
- Versions, The Lock File And Provider Aliases — HashiCorp Terraform Associate (004) Exam Prep
- State: Terraform's Memory Of What It Built — HashiCorp Terraform Associate (004) Exam Prep
- Sensitive Data, Ephemeral Values And Secrets From Vault — HashiCorp Terraform Associate (004) Exam Prep
- Where Modules Come From — HashiCorp Terraform Associate (004) Exam Prep
- Runs In HCP Terraform: The cloud Block And Remote Execution — HashiCorp Terraform Associate (004) Exam Prep
- Collaboration And Governance: Teams, Policies, Registry And Health — HashiCorp Terraform Associate (004) Exam Prep
- VCS, CLI And API Workflows: Speculative Plans And Run Triggers — HashiCorp Terraform Associate (004) Exam Prep
- Git And VS Code: Clone, Commit, Push, And The Dev Container — RHCE in Ansible (EX294): Automate Red Hat Systems
- Drill: People, Passwords And sudo From The Vault — RHCE in Ansible (EX294): Automate Red Hat Systems