如何基于原始字典结构使用Ansible lineinfile任务以DRY方式配置systemd配置文件

Great question—keeping your configuration in that clean nested dictionary format is totally doable without restructuring it into lists. The key is to properly unpack both levels of your dictionary so the lineinfile module can access each individual setting for each systemd service.

Here's the working playbook task that leverages your original systemd_configurations variable structure:

- name: Configure systemd services from nested dictionary
  lineinfile:
    path: "/etc/systemd/{{ item.0.key }}.conf"
    regexp: "^#?{{ item.1.key }}="
    line: "{{ item.1.key }}={{ item.1.value }}"
    backrefs: yes
  loop: "{{ systemd_configurations | dict2items | subelements('value', 'dict2items') }}"

Let me break down how this works step by step so you understand the logic:

1. Unpack the outer dictionary: systemd_configurations | dict2items converts your top-level dictionary into a list of objects like {key: "journald", value: {SystemMaxUse: "100M", Storage: "persistent"}}.
2. Unpack inner dictionaries with subelements: The subelements('value', 'dict2items') part takes each inner value dictionary (like the settings for journald) and converts it into a list of key-value pairs, then flattens the structure. Each loop iteration gets:
   • item.0: The outer service object (e.g., {key: "journald", value: {...}})
   • item.1: A single setting key-value pair (e.g., {key: "SystemMaxUse", value: "100M"})
3. Robust regex matching: The ^#?{{ item.1.key }}= regex matches lines that either start with the commented-out version (#SystemMaxUse=) or the active version (SystemMaxUse=), ensuring we replace existing settings regardless of their current state.
4. Safe replacement with backrefs: Adding backrefs: yes guarantees that if we match a commented line, we replace it with the uncommented, correctly formatted setting line.

If you prefer a more explicit approach using json_query (easier to read for complex nested structures), here's an alternative version:

- name: Configure systemd services (json_query variant)
  lineinfile:
    path: "/etc/systemd/{{ item.0.service }}.conf"
    regexp: "^#?{{ item.1.key }}="
    line: "{{ item.1.key }}={{ item.1.value }}"
    backrefs: yes
  loop: "{{ systemd_configurations | dict2items | json_query('[].{service: key, settings: value | dict2items}') | subelements('settings') }}"

This does the same job but renames the outer key to service via json_query for clearer variable names in the task.

Sticking with your original dictionary structure keeps things maintainable—you can clearly see each setting’s key and value without manually constructing strings, which aligns perfectly with the DRY principle you’re aiming for.

内容的提问来源于stack exchange，提问作者user226335