TARGETS
  • Read Me
  • Introduction
    • Motivation
    • Project Goals
    • What is Targets?
    • Who is Targets for?
    • Common Use Cases
    • What is a "target"?
    • What is a "composition"?
    • What is an "operation"?
    • What is a "spec"?
    • What does a Targets implementation look like?
    • Background
  • Learn Targets
    • Hello World
    • Config - Part 1
    • Config - Part 2
    • Bindings
    • Composition
    • Loaders
    • Project Structure
    • More Examples
  • Reference
    • System Requirements
    • Installation
    • Configuration
    • Settings
    • Global Store
    • Scheduler
    • Operations
      • Binding Operations
      • Predicating Operations
      • Debugging Operations
    • TTY Mode
Powered by GitBook
On this page
  1. Reference

Operations

PreviousSchedulerNextBinding Operations

Last updated 6 years ago

Operations are meta-targets which handle side-effects. They provide an explicit/declarative mechanism for altering config, dictating control flow, toggling states/modes and otherwise affecting the behavior of your workflows.

Syntax

All operations start with an at sign (@) followed by the operation's name. Optionally, a forward-slash (/) may follow the name after which arguments to the operation may be included with each argument delimited by two colons (::).

Operation without arguments:

@{operation name}

Operation with single argument:

@{operation name}/{argument}

Operation with multiple arguments:

@{operation name}/{argument}::{argument}[::{...rest}]

Binding Operations
Predicating Operations
Debugging Operations