You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,6 +94,8 @@ This is an example deployment for using OTF in an AWS environment, using BMC Con
94
94
95
95
# Configuration
96
96
97
+
> For a step-by-step guide to getting started, see [docs/usage.md](docs/usage.md).
98
+
97
99
There are several ways to customise the running of tasks.
98
100
99
101
## Command Line Arguments
@@ -245,6 +247,8 @@ Again this will be logged to show you that the override is being applied.
245
247
246
248
## Lookup plugins
247
249
250
+
> For full plugin reference and a guide to writing your own, see [docs/plugins/lookup.md](docs/plugins/lookup.md).
251
+
248
252
Static variables are useful, however sometimes you need to look up something a bit more dynamic, or secret, that you don't want to hard code into the variables file.
249
253
250
254
There are 2 default lookup plugins available:
@@ -350,6 +354,8 @@ The task definitions themselves live under the `cfg` directory, and any number o
350
354
351
355
## Transfers
352
356
357
+
> For a full attribute reference, see [docs/task-types.md#transfers](docs/task-types.md#transfers).
358
+
353
359
Transfers consist of a `source` definition, and an optional `destination`.
354
360
355
361
The easiest way to see usage is to look at the examples under the `examples` directory
@@ -442,6 +448,8 @@ An explanation of what's going on in the order it will handled:
442
448
443
449
## Executions
444
450
451
+
> For a full attribute reference, see [docs/task-types.md#executions](docs/task-types.md#executions).
452
+
445
453
Executions are the simplest task to configure. They consist of a list of hosts to run on, the username to run/connect as, and the command to run.
446
454
447
455
Executions do not currently have a timeout, so can in theory run forever, or until they are killed. If a timeout is required, either use a wrapper script on the host the command is being executed on, or they should be wrapped inside a batch.
@@ -467,6 +475,8 @@ If multiple `hosts` are defined, a thread is spawned in parallel for each host.
467
475
468
476
## Batches
469
477
478
+
> For a full attribute reference, see [docs/task-types.md#batches](docs/task-types.md#batches).
479
+
470
480
Batches are a little more complex. They do not contain any task definitions, only the list, and order of execution for each task.
471
481
472
482
A batch task can have multiple options set that determine the execution order and conditions, as well as how failures and task reruns are handled.
@@ -542,6 +552,8 @@ Provides transfer and execution addons:
542
552
543
553
## Developing your own addon/plugin
544
554
555
+
> For a full developer reference including package layout, abstract method signatures, schema discovery, and a worked example, see [docs/addons.md](docs/addons.md).
556
+
545
557
When using external libraries, be sure to add `opentaskpy.otflogging.set_log_file("<PACKAGE>")` somewhere to ensure that any additional logs from the 3rd party library make their way into the OTF logs.
0 commit comments