Skip to content

Commit cd398aa

Browse files
authored
Add new/updated docs (#153)
1 parent 4798b7a commit cd398aa

6 files changed

Lines changed: 1438 additions & 10 deletions

File tree

CHANGELOG.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,9 @@
11
# Changelog
22

3+
# No release
4+
5+
- Update docs
6+
37
# v26.10.0
48

59
- Resolve Jinja-templated lookup arguments before invoking lookup plugins.

README.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -94,6 +94,8 @@ This is an example deployment for using OTF in an AWS environment, using BMC Con
9494

9595
# Configuration
9696

97+
> For a step-by-step guide to getting started, see [docs/usage.md](docs/usage.md).
98+
9799
There are several ways to customise the running of tasks.
98100

99101
## Command Line Arguments
@@ -245,6 +247,8 @@ Again this will be logged to show you that the override is being applied.
245247
246248
## Lookup plugins
247249

250+
> For full plugin reference and a guide to writing your own, see [docs/plugins/lookup.md](docs/plugins/lookup.md).
251+
248252
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.
249253

250254
There are 2 default lookup plugins available:
@@ -350,6 +354,8 @@ The task definitions themselves live under the `cfg` directory, and any number o
350354

351355
## Transfers
352356

357+
> For a full attribute reference, see [docs/task-types.md#transfers](docs/task-types.md#transfers).
358+
353359
Transfers consist of a `source` definition, and an optional `destination`.
354360

355361
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:
442448

443449
## Executions
444450

451+
> For a full attribute reference, see [docs/task-types.md#executions](docs/task-types.md#executions).
452+
445453
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.
446454

447455
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.
467475

468476
## Batches
469477

478+
> For a full attribute reference, see [docs/task-types.md#batches](docs/task-types.md#batches).
479+
470480
Batches are a little more complex. They do not contain any task definitions, only the list, and order of execution for each task.
471481

472482
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:
542552

543553
## Developing your own addon/plugin
544554

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+
545557
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.
546558

547559
### Lookup Plugins

0 commit comments

Comments
 (0)