saltlabstech/slap-ansible repository overview

A collection of Docker image builds for use with VMware vRealize Automation Code Stream CI tasks

Prerequisites The Ansible control machine must use an Ansible version. See the vRealize Automation Support Matrix for information about supported versions. The user must have read/write access to the directory where the Ansible inventory file is located. In addition, the user must have read/write access to the inventory file, if it exists already. If you are using a non-root user with the sudo option, ensure that the following is set in the sudoers file: Defaults:user_name !requiretty

and

username ALL=(ALL) NOPASSWD: ALL

Ensure that host key checking is disabled by setting host_key_checking = False at /etc/ansible/ansible.cfg or ~/.ansible.cfg. Ensure that the vault password is set by adding the following line to the /etc/ansible/ansible.cfg or ~/.ansible.cfg file: vault password_file = /path/to/password_file The vault password file contains the password in plain text and is used only when cloud templates or deployments provide the username and password combination to use between ACM and the node as show in the following example. echo 'myStr0ng9@88w0rd' > /.ansible_vault_password.txt echo 'ANSIBLE_VAULT_PASSWORD_FILE=/.ansible_vault_password.txt' > /.profile # Instead of this way, you can also set it setting 'vault_password_file=/.ansible_vault_password.txt' in either /etc/ansible/ansible.cfg or ~/.ansible.cfg To avoid host key failures while trying to run playbooks, it is recommended that you include the following settings in /etc/ansible/ansible config. [paramiko_connection] record_host_keys = False

[ssh_connection] #ssh_args = -C -o ControlMaster=auto -o ControlPersist=60s ssh_args = -o UserKnownHostsFile=/dev/null # If you already have any options set for ssh_args, just add the additional option shown here at the end.