azure 如何基于集合事实将多个可能条件合并为一个

k5hmc34c  于 2022-11-17  发布在  其他
关注(0)|答案(1)|浏览(120)

在浏览Ansible的其中一个SO post时,我对set_fact在不同条件检查中的用法感兴趣。
然而,我根据我的方法在帖子上回答了问题,但是,我仍然看到,对于类似的任务,如确定locationresource groupvnet,俱乐部的多个条件可以有所改进。
下面是playbook和变量文件azure_vars.yml
行动手册:

---
- name: create azure vm
  hosts: localhost
  connection: local
  tasks:
   -  include_vars: azure_vars.yml

   - set_fact:
      host: "{{ azure_vm_name.split('.') }}"

   - set_fact:
       domain: "{{ host.1 }}.{{ host.2 }}"

   - name: Domain
     debug:
      msg: "{{ domain }}"

   - set_fact:
      location: "{{ azure_location[0] }}"
     when: 'domain == azure_domain[0]'

   - set_fact:
      location: "{{ azure_location[1] }}"
     when: 'domain == azure_domain[1]'

   - set_fact:
      location: "{{ azure_location[2] }}"
     when: 'domain == azure_domain[2]'

   - name: Location
     debug:
      msg: "{{ location }}"

   - set_fact:
      res_group: "{{ azure_res_group[0] }}"
     when: 'domain == azure_domain[0]'

   - set_fact:
      res_group: "{{ azure_res_group[1] }}"
     when: 'domain == azure_domain[1]'

   - set_fact:
      res_group: "{{ azure_res_group[2] }}"
     when: 'domain == azure_domain[2]'

   - name: Resource Group
     debug:
      msg: "{{ res_group }}"

   - set_fact:
      vnet: "{{ azure_nprod_vnet }}"
     when: 'domain == azure_domain[0]'

   - set_fact:
      vnet: "{{ azure_prod03_vnet }}"
     when: 'domain == azure_domain[2]'

   - set_fact:
      vnet: "{{ azure_prod02_vnet }}"
     when: 'domain == azure_domain[1]'

   - name: Vnet
     debug:
      msg: "{{ vnet }}"

变量文件:此文件包含所有变量,这些变量将成为playbook的一部分,并作为任务部分下的include_vars导入。

  • Azure _变量.yml*
---
azure_nprod_vnet: "/subscriptions/XXXXXXXX-XXX-XXXX-XXXX-XXXXXXXXXXXX/resourceGroups/rg001/providers/Microsoft.Network/virtualNetworks/vnet"
azure_prod02_vnet: "/subscriptions/XXXXXXXX-XXX-XXXX-XXXX-XXXXXXXXXXXX/resourceGroups/rg003/providers/Microsoft.Network/virtualNetworks/vnet"
azure_prod03_vnet: "/subscriptions/XXXXXXXX-XXX-XXXX-XXXX-XXXXXXXXXXXX/resourceGroups/rg002/providers/Microsoft.Network/virtualNetworks/vnet"

    
# Azure domain
azure_domains:
  - us-sea01
  - us-azrc2
  - eu-azrc1

# Resource group
azure_res_group:
  - rg001
  - rg002
  - rg003

# Azure locations
azure_location:
  - westus2
  - southcentralus
  - westeurope

预计会是俱乐部下面三个变成一个的条件:

- set_fact:
    location: "{{ azure_location[0] }}"
  when: 'domain == azure_domain[0]'

- set_fact:
    location: "{{ azure_location[1] }}"
  when: 'domain == azure_domain[1]'

- set_fact:
    location: "{{ azure_location[2] }}"
  when: 'domain == azure_domain[2]'

可能是这样的:

- set_fact:
    location:
      - azure_location[0]
      - azure_location[1]
      - azure_location[2]
  when:
    - 'domain == azure_domain[0]
    - 'domain == azure_domain[1]
    - 'domain == azure_domain[2]
btqmn9zl

btqmn9zl1#

您可以使用loopzip过滤器来解决此问题,或者使用with_together(如果您想让您的行动手册适应未来的发展,则不再推荐使用这种老式方法)。
根据行动手册:

- hosts: all
  vars:
    azure_vm_name: foo.bar.us-sea01.whatever.example.org

  tasks:
    - include_vars: azure_vars.yml

    - set_fact:
        host: "{{ azure_vm_name.split('.') }}"

    - set_fact:
        domain: "{{ host.2 }}"

    - name: Domain
      debug:
        msg: "{{ domain }}"

    - set_fact:
        location: "{{ item.1 }}"
      loop: "{{ azure_domains | zip(azure_location) | list }}"
      when: 'domain == item.0'

    - name: Location
      debug:
       msg: "{{ location }}"

以及变量文件 azure_vars.yml

azure_domains:
  - us-sea01
  - us-azrc2
  - eu-azrc1

azure_location:
  - westus2
  - southcentralus
  - westeurope

这就产生了总结:

PLAY [all] *******************************************************************************************************

TASK [Gathering Facts] *******************************************************************************************
ok: [localhost]

TASK [include_vars] **********************************************************************************************
ok: [localhost]

TASK [set_fact] **************************************************************************************************
ok: [localhost]

TASK [set_fact] **************************************************************************************************
ok: [localhost]

TASK [Domain] ****************************************************************************************************
ok: [localhost] => {
    "msg": "us-sea01"
}

TASK [set_fact] **************************************************************************************************
ok: [localhost] => (item=['us-sea01', 'westus2'])
skipping: [localhost] => (item=['us-azrc2', 'southcentralus']) 
skipping: [localhost] => (item=['eu-azrc1', 'westeurope']) 

TASK [Location] **************************************************************************************************
ok: [localhost] => {
    "msg": "westus2"
}

PLAY RECAP *******************************************************************************************************
localhost                  : ok=7    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0

也就是说,还有另一种可能性,利用Python的Ansible功能,你可以使用列表的index()方法来定位azure_location中的元素,该元素与azure_domains中的domain位置相同。
例如,如果domain位于azure_domains的位置2,则会得到azure_location中位置2的元素。
根据行动手册:

- hosts: all
  vars:
    azure_vm_name: foo.bar.us-sea01.whatever.example.org

  tasks:
    - include_vars: azure_vars.yml

    - set_fact:
        host: "{{ azure_vm_name.split('.') }}"

    - set_fact:
        domain: "{{ host.2 }}"

    - name: Domain
      debug:
        msg: "{{ domain }}"

    - set_fact:
        location: "{{ azure_location[azure_domains.index(domain)] }}"

    - name: Location
      debug:
       msg: "{{ location }}"

和相同的变量文件 azure_vars.yml,这将生成以下摘要:

PLAY [all] ******************************************************************************************************************

TASK [Gathering Facts] ******************************************************************************************************
ok: [localhost]

TASK [include_vars] *********************************************************************************************************
ok: [localhost]

TASK [set_fact] *************************************************************************************************************
ok: [localhost]

TASK [set_fact] *************************************************************************************************************
ok: [localhost]

TASK [Domain] ***************************************************************************************************************
ok: [localhost] => {
    "msg": "us-sea01"
}

TASK [set_fact] *************************************************************************************************************
ok: [localhost]

TASK [Location] *************************************************************************************************************
ok: [localhost] => {
    "msg": "westus2"
}

PLAY RECAP ******************************************************************************************************************
localhost                  : ok=7    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0

它没有使用循环,所以更容易重述。

相关问题