CSV deliver
Appends each record to a CSV file, one column per step variable. The file gets a header on first write.
| Connector | csv/deliver |
|---|---|
| Role | deliver |
| Records | person |
| Tier | built in |
| Credential | none |
| Cost | $0 |
| Source | internal/adapters |
Use it
It ships inside the binary. In a pipeline file:
steps:
- id: deliver
use: csv/deliver
with:
path: PATHReplace the placeholder:
PATH: cSV file to write; created with a header, appended across runs
gtme plan pipeline.yaml checks the credential is set and that every field this step needs is provided by a step before it, without calling anyone.
Needs
Whatever fields the step's uses: line names. The runner checks them at plan time.
Provides
Nothing. A deliver step writes to the target and records a receipt.
Config
| Key | Type | What it does |
|---|---|---|
path required | string | CSV file to write; created with a header, appended across runs |
entity_type | string |
On this page, connector means what gtme calls an adapter. This one is a process adapter compiled into the binary. Two adapter tiers explains the difference.