"Ansible managed" in Conventions and Evolinux.yml
This commit is contained in:
parent
18536ee6aa
commit
4b7ac01574
|
@ -1,5 +1,11 @@
|
|||
# Conventions
|
||||
|
||||
## Ansible managed, or not?
|
||||
|
||||
When a server has just a few modifications made via Ansible, it's often enough to put a block marker (if just a section of a file is managed by Ansible) or a `{{ ansible_managed }}` tag at the top of the files (if this file is fully managed by Ansible).
|
||||
|
||||
When a server is fully managed by Ansible, it's even better to use the `ansible-managed` role. It can be found in the **ansible-roles** repository. For the moment it only changes the "Message Of The Day" file (in `/etc/motd`). Don't forget to customize the `project_repositopy` variable ; it is used in this file.
|
||||
|
||||
## Roles
|
||||
|
||||
We can use the `ansible-galaxy init` command to bootstrap a new role :
|
||||
|
|
|
@ -17,6 +17,8 @@
|
|||
- "{{ roles }}/nagios-nrpe"
|
||||
- "{{ roles }}/listupgrade"
|
||||
- "{{ roles }}/evomaintenance"
|
||||
# Consider enabling the ansible-managed role
|
||||
# - "{{ roles }}/ansible-managed"
|
||||
|
||||
|
||||
post_tasks:
|
||||
|
|
Loading…
Reference in a new issue