Module render 

areev trigger render — emit scheduler config, never create it.

These are templates, not API clients. Areev does not hold cloud credentials and does not create cloud resources: provisioning a Cloud Scheduler job or an EventBridge rule needs IAM permission to create resources, which is a large privilege escalation for a memory engine, and it buys a multi-cloud abstraction treadmill for very little differentiation. You apply the output with whatever you already use for infrastructure.

The heartbeat is deliberately coarse

The rendered interval is the greatest common divisor of the declared intervals, floored at 60s — not the shortest interval. The memory owns the real cadence, so the heartbeat only has to be fine enough not to add meaningful lag. Rendering a 30-second cron because one trigger asked for 30 seconds would put the schedule back in the crontab, which is the thing this feature exists to stop.

Structs

RenderContext

What the rendered config should invoke.

Constants

TARGETS

Every target render accepts.

Functions

heartbeat_secs

Pick the heartbeat for a set of declarations.

render

Render config for target.