ansible-collections/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2025-08-03 20:54:24 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 10

roles/x/scripts support: update docs

Browse source 
also added example on where regular tasks fit in
This commit is contained in:
Serge van Ginderachter 2013-05-24 22:42:24 +02:00
commit 0224dc464d
2 changed files with 7 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docsite/latest/rst/bestpractices.rst
View file

@ -48,6 +48,8 @@ The top level of the directory would contain files and directories like so::
main.yml # <-- tasks file can include smaller files if warranted main.yml # <-- tasks file can include smaller files if warranted
handlers/ # handlers/ #
main.yml # <-- handlers file main.yml # <-- handlers file
scripts/ #
foo.sh # <-- script files for use with the script resource
templates/ # <-- files for use with the template resource templates/ # <-- files for use with the template resource
ntp.conf.j2 # <------- templates end in .j2 ntp.conf.j2 # <------- templates end in .j2
files/ # files/ #

5
docsite/latest/rst/playbooks.rst
View file

@ -463,12 +463,14 @@ Example project structure::
roles/ roles/
common/ common/
files/ files/
scripts/
templates/ templates/
tasks/ tasks/
handlers/ handlers/
vars/ vars/
webservers/ webservers/
files/ files/
scripts/
templates/ templates/
tasks/ tasks/
handlers/ handlers/
@ -488,6 +490,7 @@ This designates the following behaviors, for each role 'x':
- If roles/x/handlers/main.yml exists, handlers listed therein will be added to the play - If roles/x/handlers/main.yml exists, handlers listed therein will be added to the play
- If roles/x/vars/main.yml exists, variables listed therein will be added to the play - If roles/x/vars/main.yml exists, variables listed therein will be added to the play
- Any copy tasks can reference files in roles/x/files/ without having to path them relatively or absolutely - Any copy tasks can reference files in roles/x/files/ without having to path them relatively or absolutely
- Any script tasks can reference scripts in roles/x/sripts/ without having to path them relatively or absolutely
- Any template tasks can reference files in roles/x/templates/ without having to path them relatively or absolutely - Any template tasks can reference files in roles/x/templates/ without having to path them relatively or absolutely
If any files are not present, they are just ignored. So it's ok to not have a 'vars/' subdirectory for the role, If any files are not present, they are just ignored. So it's ok to not have a 'vars/' subdirectory for the role,
@ -526,6 +529,8 @@ If you want to define certain tasks to happen before AND after roles are applied
- shell: echo 'hello' - shell: echo 'hello'
roles: roles:
- { role: some_role } - { role: some_role }
tasks:
- shell: echo 'still busy'
post_tasks: post_tasks:
- shell: echo 'goodbye' - shell: echo 'goodbye'