oci-fn-file-manifest-writer

What it does

The first useful run is a manifest that another system could read immediately. That makes the starter repo feel like a real boundary pattern instead of only a trigger demo.

Try it locally

python3 - <<'PY'
import json
from func import build_manifest
payload = json.load(open('sample-event.json'))
print(json.dumps(build_manifest(payload), indent=2))
PY

Example output

{
  "generated_at": "2026-05-05T16:03:11.575412+00:00",
  "file_count": 5,
  "groups": {
    "claims": 2,
    "finance": 2,
    "images": 1
  },
  "extensions": {
    "csv": 2,
    "json": 2,
    "png": 1
  }
}

Where it helps

Use this when an event-driven workflow should condense a file batch into one compact handoff for a queue worker, reconciliation job, or downstream ingest step.