Skip to content

Report configured reclamation window in provider status responses #635

@linear

Description

@linear

Why

Exposing the field in the API is not enough — the running provider must report its configured value so inventory and bid-screening clients can rely on it.

What

Provider status responses report the provider's configured reclamation window. Providers without a configured window omit the field.

Flows that should work:

  1. REST /status includes reclamation_window when configured.
  2. gRPC GetStatus and StreamStatus include Status.reclamation_window.

Acceptance Criteria

  • /status includes reclamation_window when configured, and omits it when not.
  • gRPC GetStatus and StreamStatus include Status.reclamation_window matching the configured --reclamation-window.
  • Existing bidengine behavior is unchanged.
  • Tests cover provider REST/gRPC status wiring.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    Backlog (not prioritized)

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions