d81a519f25
* Remove .travis.yml files from galaxy init skeletons These files have existed for many years but in light of the recent circumstances around Travis, we should not include them by default in the galaxy init skeletons. * Add breaking_changes changelog fragment with recommendation to use a custom skeleton if the .travis.yml file is still needed. Co-authored-by: s-hertel <19572925+s-hertel@users.noreply.github.com> |
2 years ago | |
|---|---|---|
| .. | ||
| defaults | 8 years ago | |
| files | 8 years ago | |
| handlers | 8 years ago | |
| meta | 5 years ago | |
| tasks | 8 years ago | |
| templates | 8 years ago | |
| templates_extra | 8 years ago | |
| tests | 8 years ago | |
| vars | 8 years ago | |
| README.md | 8 years ago | |
| inventory | 8 years ago | |
README.md
Role Name
A brief description of the role goes here.
Requirements
Any pre-requisites that may not be covered by Ansible itself or the role should be mentioned here. For instance, if the role uses the EC2 module, it may be a good idea to mention in this section that the boto package is required.
Role Variables
A description of the settable variables for this role should go here, including any variables that are in defaults/main.yml, vars/main.yml, and any variables that can/should be set via parameters to the role. Any variables that are read from other roles and/or the global scope (ie. hostvars, group vars, etc.) should be mentioned here as well.
Dependencies
A list of other roles hosted on Galaxy should go here, plus any details in regards to parameters that may need to be set for other roles, or variables that are used from other roles.
Example Playbook
Including an example of how to use your role (for instance, with variables passed in as parameters) is always nice for users too:
- hosts: servers
roles:
- { role: username.rolename, x: 42 }
License
BSD
Author Information
An optional section for the role authors to include contact information, or a website (HTML is not allowed).