v0.3.0

v0.3.0 — discovery source identity, and the attributes Terraform coul…

v0.2.1

Fixed:
  The API now auto-routes blocked to the project default destination
  alongside down, fail and recovery. blocked means an agent has stopped
  mid-task and is waiting on a human, and it was silent by default.

  defaultAlertEvents tracks that set exactly. Left at three events, a
  blocked route declared in the same apply as its monitor would collide
  with the one the server had just created and fail as an adoption
  conflict, so this release must be used with an API deployed on or after
  2026-08-08.

v0.2.0

New resource:
  lastping_agent -- register an agent and see its fleet state.

New on lastping_monitor:
  agent_id       -- attach a monitor to an agent (in-place update).
  assertion {}   -- assert on the ping body; a failing assertion turns a
                    success into a fail, so a job that exits zero and does
                    nothing stops reading as healthy.
  metric_guard {} -- alert when a reported numeric crosses a ceiling over a
                    window (sum/max/avg). window_s caps at 7 days.

Fixed:
  lastping_route and lastping_alert_template accept blocked and note. Six
  event types were declared where the API accepts eight, so blocked -- an
  agent waiting on a human -- could not be routed at all.

v0.1.3

Monitor resource gains two detection settings:

- failure_threshold — consecutive failures before an incident opens
  (retry-before-alert). Gates the fail cause only; a success resets it.
- max_runtime_s — maximum duration of a single run. Replaces grace_s for the
  overrun deadline only; the silence rule and first-run seed still use grace_s.
  Not supported on http monitors, rejected at plan time.

Routes and alert templates accept two new event types:

- success — fires only on a successful run completion.
- started — fires when a run begins.

Required by the API's Terraform HCL exporter, which already emits
failure_threshold and max_runtime_s. Older providers reject such a file
entirely with "Unsupported argument".

v0.1.2

v0.1.2

v0.1.1

v0.1.1

v0.1.0

v0.1.0