group_vars & host_vars

Lesson 8 gave you groups. This lesson gives those groups configuration — and the mechanism is two directories, group_vars and host_vars , that live next to your inventory file. The entire trick is in the filenames:

inventory/
├── hosts.yml           # your lesson-8 inventory: web, db, all the groups
├── group_vars/
│   ├── all.yml         # every host in the inventory — keep it minimal
│   └── web.yml         # every host in the web group
└── host_vars/
    └── web01.yml       # exactly one machine: web01

There is no import line, no path setting, no reference from the inventory. Ansible auto-loads each file by matching its name against your group and host names: group_vars/web.yml applies to every host in web, host_vars/web01.yml applies to the single host web01, and group_vars/all.yml applies to everything, because every host belongs to the built-in all group. Inside, a vars file is nothing but YAML keys and values:

# loaded automatically for every host in the web group
app_env: staging
http_port: 8080
motd_message: 'managed by ansible - do not hand-edit'

Where environment config lives

The rule of thumb is blunt: environment config lives here. Ports, service endpoints, tuning values, anything that varies between staging and production — that belongs in group_vars, not hardcoded into a playbook and not scattered across the inventory file itself. Later, when roles arrive in Unit 6, you’ll see the full division of labour: user-tunable defaults in the role, environment values in group_vars.

Two habits separate tidy repos from haunted ones:

• Keep group_vars/all.yml minimal. A value in all.yml touches every host in the inventory, so it earns its place only by being genuinely universal. Environment-specific values belong in the environment’s own inventory directory — more on that below.
• Use host_vars/ sparingly, for values true of one machine only. If you’re writing the same key into three host files, those hosts are telling you they want to be a group.

Your inventory now says both who your hosts are and what is true about them — and everything loads by naming convention, with zero wiring. Real repos push this one step further: a separate inventory directory per environment (inventories/production/, inventories/staging/), each with its own group_vars and host_vars, so staging values can never bleed into prod. That structure — plus the patterns that pick which hosts a run actually touches — is lesson 10.