Skip to content

v.0.0.4

Choose a tag to compare

View all tags
@denyska-oai denyska-oai released this 13 Feb 23:44
· 164 commits to master since this release
v.0.0.4
1e6717b

Executive summary

Since v.0.0.3, this update changes runtime behavior in three areas: Harpoon target discovery is now intent-aware, OAuth discovery output is grouped to match backend expectations, and readiness now reflects actual OAuth initialization status.

For OAuth-enabled deployments, this update is required (not optional).

Major changes

1) Harpoon target discovery is now intent-aware

list_targets now supports input filters and richer metadata:

  • Targets now expose category, source, and tags.
  • Callers can filter by categories, sources, and tags.
  • OAuth-discovered targets now carry role-specific tags so clients can resolve endpoints by purpose, not by label naming.

Operational impact:

  • Integrations can select targets by intent and metadata instead of static label conventions.
  • Admin UI now shows target provenance and role context directly.

2) OAuth discovery output now includes endpoint grouping (backend-aligned)

OAuth discovery now produces grouped auth-server endpoint records and includes revocation endpoint metadata.

Why this matters:

  • Backend behavior has been updated to consume grouped OAuth discovery data.
  • Grouping keeps related authorization-server endpoints tied together as one bundle throughout processing.

Operational impact:

  • OAuth users must run this version (or newer) to stay compatible with backend OAuth discovery handling.

3) Readiness now reflects OAuth startup completion

Readiness is no longer always green at process start:

  • /readyz returns 503 (oauth discovery pending) until OAuth discovery finishes.
  • The readiness metric now tracks this state (0 while pending, 1 when ready).

Operational impact:

  • Startup and rollout signals now better match real OAuth availability.

4) Connection behavior under load is more stable

Connection/client initialization and reconnect behavior are improved to avoid duplicate setup work and stale shared connections during concurrent traffic.

Operational impact:

  • Fewer transient startup/connectivity issues under concurrent command load.
  • Cleaner recovery after connection close/reopen cycles.

Migration note

  • If you use OAuth discovery flows, this release is mandatory. Backend now expects grouped OAuth discovery records, so staying on pre-grouping client behavior can break OAuth discovery-dependent flows.

Full Changelog: v.0.0.3...v.0.0.4

Assets 9
Loading