Tutorial: Quickstart File Store Roundtrip
This tutorial walks through the built-in Quickstart: File Store Roundtrip workflow (quickstart-file-store-roundtrip), which proves an end-to-end deployment lifecycle using a durable hop on local disk.
What you’ll build
The workflow is a simple two-stage system:
echo → file-store (write) → file-store (read) → printYou should see:
- files created under the configured file-store path, and
- events printed to worker logs.
Prerequisites
- A licensed LyftData deployment with the Deployment Manager enabled.
- At least one online worker in a worker group.
- A filesystem path on the worker host that the worker process can read/write.
Step 1: Find the workflow in the Catalog
- Open Catalog.
- Filter to Workflows.
- Search for Quickstart: File Store Roundtrip (or
quickstart-file-store-roundtrip). - Choose the latest version and click Plan & register.
Step 2: Create the deployment
In the “create deployment” flow:
- Give the deployment a name (for example
file-store-roundtrip-demo). - Select a worker group to run it on.
- If a wizard is shown, set:
- File-store path: a directory on the worker host (for example
/var/lib/lyftdata-worker/file-store). - GUID prefix: any short prefix to keep generated file names recognizable.
- File-store path: a directory on the worker host (for example
Step 3: Plan and apply
- Review the Plan diff (jobs, transports, placement).
- Click Apply to deploy the generated jobs to the selected worker group.
Step 4: Verify data flow
- Open Workloads and confirm the deployment is running.
- Open Operate → Logs (or worker logs) and confirm events are being printed.
- On the worker host, confirm files appear under your file-store path.
Troubleshooting
- No output in logs: confirm the deployment applied successfully and the worker is online.
- File-store errors: confirm the path exists and the worker process has permissions to write to it.
- TLS/connectivity errors: verify
LYFTDATA_URLand certificate trust for the worker group (see Networking & TLS).