This commit is contained in:
sirkubax 2018-01-01 22:03:48 +01:00
parent 9a524f4cd1
commit 485db56931

View File

@ -482,7 +482,7 @@ When your job fails - it is good to be effective with debugging.
### Infrastructure as a code
You already know, that ansible-vault allow you to store your confidential data along with your code (in repository). You can go further - and define your ansible installation and configuration as-a-code.
See `environment.sh` to learn how to install the ansible itself inside a `virtualenv` that is not attached to your operating system (can be changed by non-privilages user), and as additiinal benefit - upgrading version of ansible is as easy as installing new version in new virtualenv. You can have multiple versions of Ansible present in the same time. This is very helpfull!
See `environment.sh` to learn how to install the ansible itself inside a `virtualenv` that is not attached to your operating system (can be changed by non-privilages user), and as additional benefit - upgrading version of ansible is as easy as installing new version in new virtualenv. What is more, you can have multiple versions of Ansible present in the same time. This is very helpfull!
```bash
# recreate ansible 2.x venv
@ -501,6 +501,9 @@ $ source environment.1.9.sh
```
#### become-user, become
In Ansible - to become `sudo` - use the `become` parameter. Use `become_user` to specify the username.
[Read more](http://docs.ansible.com/ansible/latest/become.html)
## Tips and tricks