@@ -78,7 +78,7 @@ <h2 id="basic-anatomy-of-rex-task-definitions"><a href="#basic-anatomy-of-rex-ta
7878< p > For the majority of use cases, I find it best to think about the most important
7979parts of task definitions like this:</ p >
8080
81- < pre > < code class ="highlight "> task < span class ="synIdentifier "> $task_name</ span > , < span class ="synIdentifier "> @targets</ span > , < span class ="synKeyword "> sub </ span > {
81+ < pre > < code class ="highlight "> < span class =" synStatement " > task</ span > < span class ="synIdentifier "> $task_name</ span > , < span class ="synIdentifier "> @targets</ span > , < span class ="synKeyword "> sub </ span > {
8282 ... < span class ="synComment "> # task steps</ span >
8383};
8484</ code > </ pre >
@@ -89,7 +89,7 @@ <h2 id="basic-anatomy-of-rex-task-definitions"><a href="#basic-anatomy-of-rex-ta
8989
9090< p > For the sake of completeness, the full situation looks more like this, though:</ p >
9191
92- < pre > < code class ="highlight "> optional_modifier task < span class ="synIdentifier "> $task_name</ span > , < span class ="synIdentifier "> @target_hosts_or_host_groups</ span > , < span class ="synKeyword "> sub </ span > {
92+ < pre > < code class ="highlight "> optional_modifier < span class =" synStatement " > task</ span > < span class ="synIdentifier "> $task_name</ span > , < span class ="synIdentifier "> @target_hosts_or_host_groups</ span > , < span class ="synKeyword "> sub </ span > {
9393 ... < span class ="synComment "> # task steps</ span >
9494}, { < span class ="synString "> task_option</ span > => < span class ="synIdentifier "> $value</ span > };
9595</ code > </ pre >
@@ -101,7 +101,7 @@ <h2 id="tasks-without-an-explicit-target"><a href="#tasks-without-an-explicit-ta
101101
102102< p > Tasks without any explicit target get executed on the local machine directly:</ p >
103103
104- < pre > < code class ="highlight "> task < span class ="synIdentifier "> $task_name</ span > , < span class ="synKeyword "> sub </ span > {
104+ < pre > < code class ="highlight "> < span class =" synStatement " > task</ span > < span class ="synIdentifier "> $task_name</ span > , < span class ="synKeyword "> sub </ span > {
105105 ... < span class ="synComment "> # task steps</ span >
106106};
107107</ code > </ pre >
@@ -130,7 +130,7 @@ <h2 id="tasks-targeting-local-explicitly"><a href="#tasks-targeting-local-explic
130130< p > One may intentionally design a task to manage the local machine by using the
131131special < code > <local></ code > hostname recognized by Rex:</ p >
132132
133- < pre > < code class ="highlight "> task < span class ="synIdentifier "> $task_name</ span > , < span class ="synString "> '<local>'</ span > , < span class ="synKeyword "> sub </ span > {
133+ < pre > < code class ="highlight "> < span class =" synStatement " > task</ span > < span class ="synIdentifier "> $task_name</ span > , < span class ="synString "> '<local>'</ span > , < span class ="synKeyword "> sub </ span > {
134134 ... < span class ="synComment "> # task steps</ span >
135135};
136136</ code > </ pre >
@@ -152,13 +152,13 @@ <h2 id="override-the-tasks-target-to-local"><a href="#override-the-tasks-target-
152152< p > and it’s also supported by the < code > on</ code > option of
153153< a href ="https://metacpan.org/pod/Rex::Commands#run_task "> < code > run_task</ code > </ a > from code:</ p >
154154
155- < pre > < code class ="highlight "> task < span class ="synIdentifier "> $task_name</ span > , < span class ="synKeyword "> sub </ span > {
155+ < pre > < code class ="highlight "> < span class =" synStatement " > task</ span > < span class ="synIdentifier "> $task_name</ span > , < span class ="synKeyword "> sub </ span > {
156156 ... < span class ="synComment "> # task steps</ span >
157157};
158158
159- task < span class ="synIdentifier "> $other_task</ span > , < span class ="synKeyword "> sub </ span > {
159+ < span class =" synStatement " > task</ span > < span class ="synIdentifier "> $other_task</ span > , < span class ="synKeyword "> sub </ span > {
160160 ... < span class ="synComment "> # task steps</ span >
161- run_task < span class ="synIdentifier "> $task_name</ span > , < span class ="synString "> on</ span > => < span class ="synString "> '<local>'</ span > ;
161+ < span class =" synStatement " > run_task</ span > < span class ="synIdentifier "> $task_name</ span > , < span class ="synString "> on</ span > => < span class ="synString "> '<local>'</ span > ;
162162 ... < span class ="synComment "> # task steps</ span >
163163};
164164</ code > </ pre >
@@ -170,15 +170,15 @@ <h2 id="disable-ssh-per-task-with-no_ssh-task"><a href="#disable-ssh-per-task-wi
170170
171171< p > The < code > no_ssh</ code > command hints individual tasks to not use SSH:</ p >
172172
173- < pre > < code class ="highlight "> no_ssh task < span class ="synIdentifier "> $task_name</ span > , < span class ="synKeyword "> sub </ span > {
173+ < pre > < code class ="highlight "> no_ssh < span class =" synStatement " > task</ span > < span class ="synIdentifier "> $task_name</ span > , < span class ="synKeyword "> sub </ span > {
174174 ... < span class ="synComment "> # task steps</ span >
175175};
176176</ code > </ pre >
177177
178178< p > This command serves as a convenience wrapper to append < code > { no_ssh => 1 }</ code > as
179179a task option, making the above the same as:</ p >
180180
181- < pre > < code class ="highlight "> task < span class ="synIdentifier "> $task_name</ span > , < span class ="synKeyword "> sub </ span > {
181+ < pre > < code class ="highlight "> < span class =" synStatement " > task</ span > < span class ="synIdentifier "> $task_name</ span > , < span class ="synKeyword "> sub </ span > {
182182 ... < span class ="synComment "> # task steps</ span >
183183}, { < span class ="synString "> no_ssh</ span > => < span class ="synNumber "> 1</ span > };
184184</ code > </ pre >
@@ -197,7 +197,7 @@ <h2 id="disable-ssh-globally-with-no_ssh"><a href="#disable-ssh-globally-with-no
197197
198198< pre > < code class ="highlight "> no_ssh;
199199
200- task < span class ="synIdentifier "> $task_name</ span > , < span class ="synKeyword "> sub </ span > {
200+ < span class =" synStatement " > task</ span > < span class ="synIdentifier "> $task_name</ span > , < span class ="synKeyword "> sub </ span > {
201201 ... < span class ="synComment "> # task steps</ span >
202202};
203203</ code > </ pre >
@@ -217,11 +217,11 @@ <h2 id="running-parts-of-a-task-within-local-blocks"><a href="#running-parts-of-
217217< p > Wrapping parts of the task steps in a < code > LOCAL{}</ code > block forces these to run on
218218the local machine instead of on the target in effect otherwise:</ p >
219219
220- < pre > < code class ="highlight "> task < span class ="synIdentifier "> $task_name</ span > , < span class ="synIdentifier "> $target</ span > , < span class ="synKeyword "> sub </ span > {
221- < span class ="synStatement "> say</ span > run < span class ="synString "> 'hostname'</ span > ; < span class ="synComment "> # say output of `hostname` from $target</ span >
220+ < pre > < code class ="highlight "> < span class =" synStatement " > task</ span > < span class ="synIdentifier "> $task_name</ span > , < span class ="synIdentifier "> $target</ span > , < span class ="synKeyword "> sub </ span > {
221+ < span class ="synStatement "> say</ span > < span class =" synStatement " > run</ span > < span class ="synString "> 'hostname'</ span > ; < span class ="synComment "> # say output of `hostname` from $target</ span >
222222
223- LOCAL {
224- < span class ="synStatement "> say</ span > run < span class ="synString "> 'hostname'</ span > ; < span class ="synComment "> # say output of `hostname` from local</ span >
223+ < span class =" synStatement " > LOCAL</ span > {
224+ < span class ="synStatement "> say</ span > < span class =" synStatement " > run</ span > < span class ="synString "> 'hostname'</ span > ; < span class ="synComment "> # say output of `hostname` from local</ span >
225225 }
226226};
227227</ code > </ pre >
0 commit comments