OCI Functions starter patterns

oci-fn-scheduled-finops-digest shows the scheduled starter pattern I want more repos to teach: end the run with one compact operational brief.

This guide exists because scheduled serverless examples often prove only that the trigger fired. The repo stays close to the more useful boundary: take a simple usage summary, identify what moved, and leave behind a digest another person can actually read or route.

Why this repo carries the track

A short site-side guide before the proof layer on GitHub.

What it proves

A scheduled starter repo gets stronger when the first run ends with one readable digest artifact instead of a vague timer demo or a wall of raw metrics.

Why it matters in this track

It extends the OCI Functions starter pattern into recurring operations work. The visible boundary here is scheduled input to concise summary artifact, which is a more believable starter outcome than a trigger alone.

What survives the first run

The FinOps digest is the artifact. It gives email, chat, or dashboard workflows one compact summary they can reuse without rerunning the analysis in each downstream step.

What the first useful success looks like

oci-fn-scheduled-finops-digest as a first useful success, not only a demo.

The first useful run is a short digest a human could read immediately. That makes the repo useful before you wire in a scheduler, email destination, or broader reporting pipeline.

Use this when a scheduled starter pattern should leave one compact reporting artifact behind first, whether the next step is email delivery, chat posting, or a broader monthly review workflow.

Quick run

python3 - <<'PY'
import json
from func import build_digest
payload = json.load(open('sample-usage-summary.json'))
print(build_digest(payload))
PY

Sample output shape

Daily FinOps Digest

Top movers:
- Object Storage +12.4% ($184)
- Functions invocations +9.1% ($63)

Watchlist:
- Analytics dev tenancy crossed budget threshold
- Backup egress returned to normal range

Where it routes next

Shows a scheduled OCI Functions workflow that turns a recurring reporting task into a small digest artifact.

Use this when a scheduled starter pattern should leave one compact reporting artifact behind first, whether the next step is email delivery, chat posting, or a broader monthly review workflow.