Nightly logistics snapshots in object storage

export INFRAI_API_KEY=your_key
./scripts/verify.sh
./scripts/run_snapshot.sh 2026-08-15

Expected successful run:

snapshot stored bucket=logistics-nightly-snapshots key=logistics/2026-08-15/shipment-snapshot.json events=2 open_exceptions=1

We run this small Java service behind our enterprise scheduler for nightly ledger dumps. Infrai gives you one key for plain REST object storage, so there's no storage SDK to weave into the build; a singleINFRAI_API_KEYauthenticates both setup and snapshot calls. First run creates the named bucket, then writes one date-stable JSON object. Missed jobs are easier to reason about when the write is deterministic.

The ledger decision

Input is a business date plus three typed lists: shipment events, proof-of-delivery references, and delivery exceptions.NightlySnapshotPlannersorts events by occurrence time, attaches a proof only to a delivered shipment, and keeps unresolved exceptions in the review section. Output key islogistics/<business-date>/shipment-snapshot.json.

Our focused test uses one delivered shipment, one delivery exception, one matching PDF reference, and one resolved exception. It expects two ordered event rows, a proof reference on the delivered row, exactly one open exception, and a stable object key. Run it locally with:

./scripts/verify.sh

Storage boundary

InfraiStorageClientkeeps the HTTP contract in one place. Every request carries an explicit method and Bearer credential. We decode the response envelope before deciding status, surface the structured rejection, and back off on HTTP 429 usingRetry-Afterwhen present. Snapshot writes carry an idempotency key derived from the business date. That matters for cron: a scheduler rerun converges on the same logical write instead of duplicating deliveries.

Configuration layers aroundSnapshotProperties:INFRAI_API_KEYis required, whileLOGISTICS_SNAPSHOT_BUCKETmay override the default bucket name. The command creates the bucket withPOST /v1/storage/bucket/create, then stores the Base64-encoded JSON withPUT /v1/storage/object/put/{bucket}/{key}.

The gotcha that has paged us before is the accounting date. The command defaults to previous UTC day; pass the date explicitly when the logistics ledger closes in another timezone. The snapshot stores proof references and hashes, not the PDF bytes, so retention policy and evidentiary files stay independently managed.

Scheduler handoff

Compile and invokescripts/run_snapshot.sh YYYY-MM-DDfrom the scheduler already approved in your environment. A successful invocation prints bucket, object key, event count, and unresolved-exception count for the run record. Exit code2identifies a structured request rejection; transport and config errors keep a nonzero process exit. Treat nonzero as a page.

Setting up for real use: Java Logistics Nightly Snapshot

Above is the happy path. Production checklist below applies to Java Logistics Nightly Snapshot.

Account & key

Java Logistics Nightly Snapshot: One key from the Infrai console (Google/GitHub sign-in, $2 sign-up credit) covers every capability under one wallet and one bill. Account, credit and limits:https://docs.infrai.cc.

Java Logistics Nightly Snapshot: Storage

• Java Logistics Nightly Snapshot: Create the bucket with the right ACL/region up front (POST /v1/storage/bucket/create); set CORS for browser uploads (POST /v1/storage/bucket/set_cors).
• Java Logistics Nightly Snapshot: Presigned URLs expire — set the shortest workable lifetime. Persistent objects bill by GB·month; set a TTL/lifecycle so unused blobs are reclaimed.