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

Global Store

Targets maintains state in a global config store. The store itself is a collection wherein each state change results in a new object being appended to the collection.

The global store houses three primary data sets under three corresponding keys: config, result and setting.

  • The state which is maintained under the config property holds the composite result of all config sources and is updated as the config is operated on by a given workflow.

  • The state which is maintained under the result property holds the resolved values from each target execution in a given workflow and is updated as new results are resolved.

  • The state which is maintained under the setting property holds any settings which have been provided via config or at runtime.

PreviousSettingsNextScheduler

Last updated 6 years ago