Chain Source

A chain source defines how a Chain gets its value. It populates the source field of a chain. There are multiple source types, and the type is specified using YAML's tag syntax.

Examples

See the Chain docs for more complete examples.

!request
recipe: login
trigger: !expire 12h
---
!command
command: ["echo", "-n", "hello"]
---
!env
variable: USERNAME
---
!file
path: ./username.txt
---
!prompt
message: Enter Password

Variants

Variant	Type	Description
`!request`	`ChainSource::Request`	Body of the most recent response for a specific request recipe.
`!command`	`ChainSource::Command`	Stdout of the executed command
`!env`	`ChainSource::Environment`	Value of an envionrment variable, or empty string if undefined
`!file`	`ChainSource::File`	Contents of the file
`!prompt`	`ChainSource::Prompt`	Value entered by the user

Request

Chain a value from the body of another response. This can reference either

Field	Type	Description	Default
`recipe`	`string`	Recipe to load value from	Required
`trigger`	`ChainRequestTrigger`	When the upstream recipe should be executed, as opposed to loaded from memory	`!never`
`section`	`ChainRequestSection`	The section (header or body) of the request from which to chain a value	`Body`

Chain Request Trigger

This defines when a chained request should be triggered (i.e. when to execute a new request) versus when to use the most recent from history.

Variant	Type	Description
`never`	None	Never trigger. The most recent response in history for the upstream recipe will always be used; error out if there is none
`no_history`	None	Trigger only if there is no response in history for the upstream recipe
`expire`	`Duration`	Trigger if the most recent response for the upstream recipe is older than some duration, or there is none
`always`	None	Always execute the upstream request

Duration is specified as an integer followed by a unit (with no space). Supported units are:

s (seconds)
m (minutes)
h (hours)
d (days)

Examples

!request
recipe: login
trigger: !never # This is the default, so the same as omitting
---
!request
recipe: login
trigger: !no_history
---
!request
recipe: login
trigger: !expire 12h
---
!request
recipe: login
trigger: !expire 30s
---
!request
recipe: login
trigger: !always

Chain Request Section

This defines which section of the response (headers or body) should be used to load the value from.

Variant	Type	Description
`body`	None	The body of the response
`header`	`string`	A specific header from the response. If the header appears multiple times in the response, only the first value will be used

Examples

!request
recipe: login
section: !header Token # This will take the value of the 'Token' header

Command

Execute a command and use its stdout as the rendered value.

Field	Type	Description	Default
`command`	`Template[]`	Command to execute, in the format `[program, ...arguments]`	Required
`stdin`	`Template`	Standard input which will be piped into the command	None

Environment Variable

Load a value from an environment variable.

Field	Type	Description	Default
`variable`	`Template`	Variable to load	Required

File

Read a file and use its contents as the rendered value.

Field	Type	Description	Default
`path`	`Template`	Path of the file to load (relative to current directory)	Required

Prompt

Prompt the user for input to use as the rendered value.

Field	Type	Description	Default
`message`	`Template`	Descriptive prompt for the user	Chain ID
`default`	`Template`	Value to pre-populated the prompt textbox. Note: Dur to a library limitation, not supported on chains with `sensitive: true` in the CLI	`null`

Slumber