Execution context#

ctx is the request-scoped object every step reads from. It holds the incoming request and the accumulated output of prior steps.

ctx
├── timestamp_epoch : int
├── request
│   ├── method  : string
│   ├── path    : map[string]string
│   ├── query   : map[string]string
│   ├── headers : map[string]string
│   └── body    : any
└── steps
    ├── <sql_step_name>
    │   ├── rows          : list(map)
    │   ├── row           : map (or null)
    │   └── rows_affected : int
    ├── <redis_step_name>
    │   └── value         : any
    ├── <starlark_step_name>
    │   └── result        : any
    └── <go_step_name>
        └── result        : any

#Request

The request object is populated at ingress and remains immutable for the life of the request.

Path parameters are bound from route templates. Catch-all parameters such as {filepath...} bind the remaining path. Header keys are lowercased at ingress.

#Steps

#Access from HCL and Starlark

In HCL expressions, steps is available as a root-level shorthand for ctx.steps. In Starlark scripts, values are accessed beneath ctx using dictionary syntax.