From 4de4d59d7a91aafa8127e6d48b303ea0abcc204b Mon Sep 17 00:00:00 2001 From: Brian Coca Date: Wed, 13 Jan 2016 18:06:19 -0500 Subject: [PATCH] changed examples to not use 'port' directive --- docsite/rst/playbooks_roles.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docsite/rst/playbooks_roles.rst b/docsite/rst/playbooks_roles.rst index 2e1173acda9..76bff6666c0 100644 --- a/docsite/rst/playbooks_roles.rst +++ b/docsite/rst/playbooks_roles.rst @@ -213,8 +213,8 @@ Also, should you wish to parameterize roles, by adding variables, you can do so, - hosts: webservers roles: - common - - { role: foo_app_instance, dir: '/opt/a', port: 5000 } - - { role: foo_app_instance, dir: '/opt/b', port: 5001 } + - { role: foo_app_instance, dir: '/opt/a', app_port: 5000 } + - { role: foo_app_instance, dir: '/opt/b', app_port: 5001 } While it's probably not something you should do often, you can also conditionally apply roles like so:: @@ -284,7 +284,7 @@ a list of roles and parameters to insert before the specified role, such as the --- dependencies: - { role: common, some_parameter: 3 } - - { role: apache, port: 80 } + - { role: apache, appache_port: 80 } - { role: postgres, dbname: blarg, other_parameter: 12 } Role dependencies can also be specified as a full path, just like top level roles::