如何在Ansible中按主机组匹配对应的模板文件？

Great question! You're actually on the right track with leveraging group-related variables—let's break down a few clean, reliable ways to map your host groups to their respective templates:

Method 1: Dynamic Template Matching with group_names #

Your initial idea of using {{ group_names }} is totally workable—you just need to account for the fact that group_names returns a list of all groups a host belongs to.

If your hosts only belong to one target group (like in your inventory example), you can simply grab the first item in the list to build your template path:

- name: Deploy group-specific configuration
  hosts: all
  tasks:
    - name: Copy group-specific config template
      ansible.builtin.template:
        src: "templates/{{ group_names[0] }}_config.yml.j2"
        dest: "/etc/my_app/config.yml"
        mode: '0644'

If you have hosts in multiple groups and need to prioritize a specific group for templating, you can add a condition or use a custom variable to define the "primary" group.

Method 2: Explicit Template Mapping via group_vars #

For more clarity (especially if your template names ever diverge from group names), define a template path variable in each group's group_vars file:

1. Create a group_vars directory alongside your playbook, with files matching your group names:

   ├── group_vars
   │   ├── group_1.yml
   │   ├── group_2.yml
   │   └── group_3.yml
   ├── templates
   │   ├── group1_config.yml.j2
   │   ├── group2_config.yml.j2
   │   └── group3_config.yml.j2
   └── playbook.yml
   

2. In each group_vars file, set the template filename:
   • group_vars/group_1.yml:

     config_template: group1_config.yml.j2
     

   • group_vars/group_2.yml:

     config_template: group2_config.yml.j2
     

3. Reference this variable in your playbook:

   - name: Deploy group-specific configuration
     hosts: all
     tasks:
       - name: Copy group-specific config template
         ansible.builtin.template:
           src: "templates/{{ config_template }}"
           dest: "/etc/my_app/config.yml"
           mode: '0644'
   

This approach is super maintainable—you can easily update template paths or add notes in the group_vars files without touching your playbook logic.

Method 3: Conditional Tasks (For Smaller Environments) #

If you prefer explicit, easy-to-read tasks (and don't have too many groups), you can use when conditions to target each group individually:

- name: Deploy group-specific configuration
  hosts: all
  tasks:
    - name: Copy config for group_1
      ansible.builtin.template:
        src: "templates/group1_config.yml.j2"
        dest: "/etc/my_app/config.yml"
        mode: '0644'
      when: "'group_1' in group_names"

    - name: Copy config for group_2
      ansible.builtin.template:
        src: "templates/group2_config.yml.j2"
        dest: "/etc/my_app/config.yml"
        mode: '0644'
      when: "'group_2' in group_names"

    - name: Copy config for group_3
      ansible.builtin.template:
        src: "templates/group3_config.yml.j2"
        dest: "/etc/my_app/config.yml"
        mode: '0644'
      when: "'group_3' in group_names"

This is straightforward but becomes less efficient as you add more groups.

Final Recommendation #

If your inventory stays simple (one group per host), go with Method 1 for brevity. If you anticipate future changes (like renaming templates or adding multi-group hosts), Method 2 is the most scalable and clean option.

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