vault ID
A label attached to Vault-encrypted data that names which password protects it, so one project can use different passwords for different environments.
In more detail
Written as label@source, for example prod@prompt, it lets Ansible pick the right password when several are available. The label is stored in the encrypted file's header. A vault ID is not access control by itself: security still comes from who can obtain each password.
Example
ansible-playbook site.yml --vault-id prod@promptRelated 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.
- vault password — The password that unlocks Vault-encrypted data; Ansible needs it at run time and it must never be stored in the repository.
- access control — The rules and mechanisms that decide who may read, use or change a resource.
- staging — A pre-production environment set up like production, where changes are tried out before they reach real users.
Taught in
- Securing Data With Ansible Vault — Ansible Configuration Management at Scale
- Vault IDs And Multiple Passwords — Ansible Configuration Management at Scale
- Users And Groups From A List, With Passwords That Settle — RHCE in Ansible (EX294): Automate Red Hat Systems
- Ansible Vault: Secrets Encrypted, Runs Without A Prompt — RHCE in Ansible (EX294): Automate Red Hat Systems
- Mock Exam, Part 2: Real Machines And The Patterns That Fail — RHCE in Ansible (EX294): Automate Red Hat Systems