Ansible遍历哈希并添加文件存在检查条件的实现咨询

Hey there! Let's work through this Ansible file existence check issue—sounds like you're stuck on getting the when condition right while iterating over your artifacts structure. Let's start by grounding this in a concrete example, since you mentioned a vars structure (I'll use a common pattern that matches your description, adjust if yours differs):

Sample Artifacts Vars Structure #

vars:
  artifacts:
    - name: "core app config"
      dest_path: "/opt/myapp/config.yaml"
    - name: "service systemd unit"
      dest_path: "/etc/systemd/system/myapp.service"
    - name: "audit log config"
      dest_path: "/etc/audit/rules.d/myapp.rules"

Elegant Playbook Solution #

Here's a clean, maintainable way to check if each defined artifact exists on the filesystem, with proper loop handling and correct when conditions:

- name: Validate artifact file existence
  hosts: your_target_inventory_group
  vars:
    artifacts:
      - name: "core app config"
        dest_path: "/opt/myapp/config.yaml"
      - name: "service systemd unit"
        dest_path: "/etc/systemd/system/myapp.service"
      - name: "audit log config"
        dest_path: "/etc/audit/rules.d/myapp.rules"

  tasks:
    - name: Collect file status for all artifacts
      ansible.builtin.stat:
        path: "{{ item.dest_path }}"
      loop: "{{ artifacts }}"
      register: artifact_status_results

    - name: Flag missing artifacts
      ansible.builtin.debug:
        msg: "⚠️ Missing required artifact: {{ item.item.name }} (expected at {{ item.item.dest_path }})"
      loop: "{{ artifact_status_results.results }}"
      when: not item.stat.exists

    # Optional: If you want to fail the play if any artifacts are missing
    - name: Fail play if critical artifacts are missing
      ansible.builtin.fail:
        msg: "Critical artifact missing: {{ item.item.name }}"
      loop: "{{ artifact_status_results.results }}"
      when: not item.stat.exists

Key Fixes & Explanations #

• Correct Loop Handling: We first use loop to iterate over your artifacts list with the stat module, which gathers filesystem info for each path. We register all these results into artifact_status_results.
• Proper when Condition: When iterating over the registered results, each item in the loop contains both the original artifact data (item.item) and the stat output (item.stat). The condition not item.stat.exists correctly checks if the file is missing.
• Separation of Concerns: Splitting the stat collection and reporting into separate tasks keeps the playbook readable—you can easily extend this (e.g., add tasks to copy missing files, send alerts, etc.) without cluttering a single task.

Common mistakes to avoid:

• Forgetting that registered loop results are stored in the .results attribute of the registered variable.
• Trying to reference item.dest_path directly in the second task's when condition (you need to use item.item.dest_path if you need the path, but item.stat.exists is the direct check for existence).

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