Skip to content

Deploying Blocks

  • Block implemented with explicit contract (inputs/outputs, errors, timeouts).
  • Config for guardrails (network allowlist, fs scope, secrets scope).
  • Observability sink (logs, traces, metrics) and dashboard access.
  1. Package the block with lockfile and runtime manifest (name, version, limits).
  2. Define environment config: secrets, allowlists, timeouts, retries, idempotency keys.
  3. Add healthcheck endpoint or command; test locally and in staging.
  4. Provision runtime (container/job) with CPU/mem limits and network policy.
  5. Wire observability: structured logs, trace context propagation, key metrics.
  6. Create rollout plan: canary cohort, success criteria, and rollback strategy.
  7. Deploy to staging → run fixtures → promote to canary → full rollout on green.
  • Healthcheck green in staging and production.
  • Canary success rate and latency within thresholds for agreed window.
  • No policy violations (network, fs, secrets) in audit logs.
  • Failing healthcheck: verify env vars, secrets scope, and network policy.
  • Timeouts: increase budget or optimize external calls; add retries with backoff.
  • Missing logs/traces: confirm instrumentation and sink credentials.