Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/jdauphant/ansible-roles
Regroupment of all my Ansible roles with git submodule + Informations
https://github.com/jdauphant/ansible-roles
Last synced: about 1 month ago
JSON representation
Regroupment of all my Ansible roles with git submodule + Informations
- Host: GitHub
- URL: https://github.com/jdauphant/ansible-roles
- Owner: jdauphant
- License: bsd-2-clause
- Created: 2014-07-16T16:39:50.000Z (over 10 years ago)
- Default Branch: master
- Last Pushed: 2015-05-20T15:44:07.000Z (over 9 years ago)
- Last Synced: 2023-03-14T16:10:32.616Z (almost 2 years ago)
- Size: 137 KB
- Stars: 1
- Watchers: 0
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
ansible-roles
=============Regroupment of all my Ansible roles with git submodule + Informations
Add this variables to you ansible.cfg
roles_path= /path/to/ansible-roles# Role conventions
- Git repository name are : ansible-role-rolename
- task name
- all task should have a name description
- all task name should tourn in form of ensure the state is ok and not made the action
- the task name don't have to include the role name
- Examples :
- Good task name: Ensure python and python-api are installed
- Bad task name: python | installation of python
- tags
- all tasks should be tag by the role name
- other standart tags are : deploy,compilation,packages,configuration,service
- tags sould set at the end of the task with this yaml form : tags: ["rolename","configuration"]
- OS
- all tasks with OS or family OS dependency should have a when condition on ansible_os_family or ansible_distribution
- especially for packages manager task
- you don't have to support all OS if you can't test it
- place OS specific task in different file if it's more than 1 task
- sudo
- use sudo only when it's not for root user