Egress
Egress is the last stage of workflow execution, during which Fuzzball exports data to an outside destination. The exported data could be output, processed data, configuration files, or anything else you want to keep when the workflow ends and the ephemeral volume is destroyed. Data egress is typically unnecessary when using persistent volumes, since the data is already saved on the volume when the workflow completes.
Fuzzball runs a volume’s egress only after every job that mounts that volume has finished, so the results are complete before they leave.
An S3 destination takes the form s3://<bucket-name>/<object-key>. Use the bucket’s plain name,
not its ARN, an access point, or an https:// URL. The S3 secret you attach to the egress supplies
the credentials, region, and endpoint; see
S3 secrets.
Fuzzball expands$FB_WORKFLOW_IDin an egress destination URI, so successive runs can write to separate locations – for examples3://my-bucket/results/$FB_WORKFLOW_ID/. This substitution applies to egress destinations only, not to any other field.
See the Fuzzfile syntax guide for the full egress
grammar.