大网数据广告活动
服务器运维问答

what does this jinja2 Filter do in Ansible? d({})

· 52CE 我爱测

I try to understand what the following codeblock does inside an Ansible-Playbook environment: '{{ inventory__environment | d({}) | combine(inventory__group_environment | d({})) | combine(inventory__host_environment | d({})) }}' F…

问题原文

原帖链接 · geets · CC BY-SA 4.0

I try to understand what the following codeblock does inside an Ansible-Playbook

environment: '{{ inventory__environment | d({})
                   | combine(inventory__group_environment | d({}))
                   | combine(inventory__host_environment  | d({})) }}'

From my understanding the environment: Keyword sets environment variables on the target host. The double-moustaches {{ xxx }} mark a jinja2 expression - Correct me if Im wrong. So there happens some kind of evaluation of what is inside those brackets. An Expression of the following format {{ x | y }} is called a 'filter' in Ansible. It works like a pipe in Bash.

So what does this special function called d() do?

已采纳解答

原帖链接 · Vladimir Botka · CC BY-SA 4.0

Q: "What does this special function called d() do?"

A: d() is shortcut for default(). For example the tasks below

    - set_fact:
        dictX: '{{ dict1 | d({}) |
                   combine(dict2 | d({})) |
                   combine(dict3 | d({})) }}'
    - debug:
        var: dictX

where dict1, dict2, and dict3 are not defined give

    "dictX": {}


The fiter combine combines the dictionaries. Let's test it. For example
  vars:

    dict1:
      key1: 'value1'
#   dict2:
#     key2: 'value2'
    dict3:
      key3: 'value3'

  tasks:

    - set_fact:
        dictX: '{{ dict1 | d({}) |
                   combine(dict2 | d({})) |
                   combine(dict3 | d({})) }}'
    - debug:
        var: dictX

give

    "dictX": {
        "key1": "value1", 
        "key3": "value3"
    }

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2020-02-28)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。