The project is divided into 3 large groups.

Group-1 - password connection

Group-2 - connection by key, Group-3 - connection by key

In ansible.cfg, the default authorization is a password. How to change behavior depending on the group?

What I tried:

  • deleted ansible.cfg settings for ask_pass
  • added ask_pass to group_vars / [all: vars], in inventory / [group_name: vars]
  • added to the playbook itself

Config:

ansible --version ansible 2.6.0 config file = Ansible/ansible.cfg configured module search path = [ u'/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python2.7/site-packages/ansible executable location = /usr/bin/ansible python version = 2.7.15 (default, May 16 2018, 17:50:09) [GCC 8.1.1 20180502 (Red Hat 8.1.1-1)] ls -gG ansible.cfg group_vars/ -rw-r--r--. 1 3257 Jul 26 20:17 ansible.cfg group_vars/: total 56 -rw-rw-r--. 1 847 Jan 26 20:02 DE.yml -rw-rw-r--. 1 681 Nov 30 2017 DK.yml -rw-rw-r--. 1 1048 Jan 26 20:02 ES.yml -rw-rw-r--. 1 1422 Jan 30 16:53 FI.yml -rw-rw-r--. 1 2145 Nov 15 2017 IE.yml -rw-rw-r--. 1 877 Feb 2 15:53 LT.yml -rw-rw-r--. 1 874 Feb 2 11:12 LV.yml -rw-rw-r--. 1 467 Jan 29 08:39 NL.yml -rw-rw-r--. 1 1939 Jan 26 20:02 NO.yml -rw-rw-r--. 1 1334 Jan 29 08:39 SE.yml lrwxrwxrwx. 1 6 Feb 3 00:34 _signoff_de.yml -> DE.yml lrwxrwxrwx. 1 6 Feb 3 00:34 _signoff_dk.yml -> DK.yml lrwxrwxrwx. 1 6 Feb 3 00:34 _signoff_es.yml -> ES.yml lrwxrwxrwx. 1 6 Feb 3 00:34 _signoff_fi.yml -> FI.yml lrwxrwxrwx. 1 6 Feb 3 00:34 _signoff_ie.yml -> IE.yml lrwxrwxrwx. 1 6 Feb 3 00:34 _signoff_lt.yml -> LT.yml lrwxrwxrwx. 1 6 Feb 3 00:34 _signoff_lv.yml -> LV.yml lrwxrwxrwx. 1 6 Feb 3 00:34 _signoff_nl.yml -> NL.yml lrwxrwxrwx. 1 6 Feb 3 00:34 _signoff_no.yml -> NO.yml lrwxrwxrwx. 1 6 Feb 3 00:34 _signoff_se.yml -> SE.yml lrwxrwxrwx. 1 8 Feb 3 00:34 _signoff_test.yml -> TEST.yml lrwxrwxrwx. 1 10 Feb 3 00:34 _signoff_uk_dcm.yml -> UK_DCM.yml lrwxrwxrwx. 1 12 Feb 3 00:34 _signoff_uk_odeon.yml -> UK_ODEON.yml lrwxrwxrwx. 1 9 Feb 3 00:34 _signoff_uk_pd.yml -> UK_PD.yml lrwxrwxrwx. 1 10 Feb 3 00:34 _signoff_uk_vue.yml -> UK_DCM.yml -rw-rw-r--. 1 2145 Jan 29 08:39 TEST.yml -rw-rw-r--. 1 2154 Feb 2 15:00 UK_DCM.yml -rw-rw-r--. 1 2202 Jan 29 08:39 UK_ODEON.yml -rw-rw-r--. 1 2034 Jan 30 15:18 UK_PD.yml lrwxrwxrwx. 1 10 Feb 3 00:34 UK-VUE.yml -> UK_DCM.yml
  • And simlinka in group_vars do not channel? I have so. - don Rumata
  • @donRumata Noble Don Arkanarsky, yes there are links, tried to add parameters to playbooks, but Ansible’s campaign “ignores” them and still uses ansible.cfg from the locale. - Hellseher
  • And if to throw out authorization by default from ansible.cfg ? Anyway, there is *_vars where everything is already pro-harkorno. And by the way. What for the managing server and what on it ansibl? I have a mulka with symlinks running on ubuntu 16.04 + official ppa with this same ansiblom. - don Rumata
  • @donRumata updated, the workstations in our department are Supermicro cpu-i7 / 16G-RAM / ssd / and there is also a combat provisioning server, everything is serious here but is spinning in VMWare on Ubunty 16.04 / - Hellseher
  • I meant "on which OS the ansibla binary is spinning." - don Rumata

1 answer 1

As I wrote in the comments, I split the project into logical groups with my configuration files, added a default group from which the roles are linked to the rest. The whole project sits under one git.

 ./ ├── aws │  ├── cache │  ├── group_vars │  ├── host_vars │  ├── inventory │  ├── library │  └── roles ├── dc │  ├── group_vars │  ├── host_vars │  ├── inventory │  ├── library │  └── roles ├── default │  └── roles ├── site │  ├── group_vars │  ├── host_vars │  ├── inventory │  ├── library │  └── roles └── var ├── cache ├── log ├── retry └── templates