Ansible中可用的hostvars在Zuul中无法访问,求替代方案
不依赖hostvars的Ansible多文件变量加载方案
问题背景
使用include_vars从多个.yaml文件加载变量时,本地Ansible Playbook运行正常,但在Zuul环境中失效。推测原因是Zuul出于安全限制,禁止直接访问hostvars,导致原方案中依赖hostvars的变量聚合逻辑无法执行。
原Playbook代码
- hosts: localhost vars: files: "{{ query('varnames', 'files_[0-9]+')| map('extract', hostvars.localhost, 'files')| flatten }}" tasks: - find: paths: "{{ playbook_dir }}" recurse: true patterns: test.yaml register: files_from_dirs - include_vars: file: "{{ item }}" name: "{{ name }}" loop: "{{ files_from_dirs.files|map(attribute='path')|list }}" loop_control: extended: true vars: name: "files_{{ ansible_loop.index }}" - debug: var: files
替代实现方案
以下两种方案均无需依赖hostvars,通过自定义字典管理加载的变量,适配Zuul环境:
方案1:合并所有变量到单一自定义字典
直接将所有文件的变量内容合并到一个全局字典中,无需生成多个独立变量:
- hosts: localhost vars: all_files_vars: {} tasks: - find: paths: "{{ playbook_dir }}" recurse: true patterns: test.yaml register: files_from_dirs - include_vars: file: "{{ item }}" name: "_temp_var" loop: "{{ files_from_dirs.files|map(attribute='path')|list }}" register: loaded_vars - set_fact: all_files_vars: "{{ all_files_vars | combine(item._temp_var) }}" loop: "{{ loaded_vars.results }}" - debug: var: all_files_vars
方案2:按文件索引存储到自定义字典子键
保留原方案的独立变量标识逻辑,将每个文件的变量存入自定义字典的对应子键中,便于区分来源:
- hosts: localhost vars: files_dict: {} tasks: - find: paths: "{{ playbook_dir }}" recurse: true patterns: test.yaml register: files_from_dirs - include_vars: file: "{{ item }}" name: "_temp_var" loop: "{{ files_from_dirs.files|map(attribute='path')|list }}" loop_control: extended: true register: loaded_vars - set_fact: files_dict: "{{ files_dict | combine({ 'files_' ~ ansible_loop.index: item._temp_var }) }}" loop: "{{ loaded_vars.results }}" loop_control: extended: true - debug: var: files_dict # 如需扁平化所有变量内容,可执行以下步骤 - set_fact: files_flattened: "{{ files_dict.values() | flatten }}" - debug: var: files_flattened
方案优势
- 完全规避
hostvars依赖,适配Zuul的安全限制 - 变量集中管理,避免全局变量污染
- 逻辑清晰,便于调试和维护
内容的提问来源于stack exchange,提问作者Eduard Florinescu
相关产品推荐
相关产品推荐

