Skip to content

feat(status): report secret lifecycles in the fleet snapshot (0.12.0) - #50

Closed
caniko wants to merge 2 commits into
trunkfrom
feat/secret-expiry
Closed

caniko wants to merge 2 commits into
trunkfrom
feat/secret-expiry

Conversation

@caniko

@caniko caniko commented Nov 15, 2026

Copy link
Copy Markdown
Owner

Adds an optional secrets section to fleetix::status::FleetStatus so the operator sees credentials that are about to expire. First consumer: canix's fleet-status producer, then the Fleetix hub's Command Center and MCP.

  • SecretInventory { scope, entries, error }, absent (None) from old producers, so a new hub can tell "not reported" from "no issues".
  • ExpiryValue: date, never or unknown. never is its own kind, distinct from undeclared, and never warns.
  • SecretState: ok, expiring, expired, never, undeclared, unverifiable, invalid. assess_secret judges against an explicit as_of with no I/O.
  • Rules: a 30-day inclusive window in UTC. Provider evidence counts as fresh for 48 hours. Missing, malformed or more than 60 seconds future evidence fails closed. A stale or failed check of a trusted earlier success keeps an already-crossed deadline visible.
  • attention() adds one per expiring, expired, invalid or unverifiable secret, plus one for an inventory error. Existing counts are unchanged.
  • Wire schema stays 1. Old JSON parses with secrets: None. FleetStatus gained a public field, so struct literals must set it, hence 0.12.0.

Tests: cargo test --lib status::tests, 8 passed, covering boundaries, never vs undeclared, freshness and deadline precedence, attention counting, wire compatibility both ways and sub-second deadlines. cargo check --workspace --all-targets and treefmt are clean.

Design: two Sol rounds (openai/gpt-6.1-sol xhigh) on top of a planner pass. Round 1 found two blockers and a should (ignored malformed attempt timestamps, deadlines kept on untrusted evidence, truncated sub-second expiry), all fixed with regressions.

Reviewed with sol-loop: 2 rounds with openai/gpt-6.1-sol. Sol verdict: approved

🤖 Generated with Claude Code

caniko and others added 2 commits November 15, 2026 16:58
FleetStatus gains an optional secrets section so the operator sees
credentials that are about to expire. Each secret carries its policy kind,
a typed expiry (date, never or unknown) and a state judged against an
explicit as_of with no I/O: a 30-day inclusive warning window, 48-hour
provider freshness, and fail-closed handling of missing, malformed or
future evidence. A never-expiring secret is its own kind, listed but not
counted; undeclared stays distinct from it. Expiring, expired, invalid and
unverifiable secrets each add one to attention(). Wire schema stays 1.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Ship the secret lifecycle section of the fleet snapshot. FleetStatus gains a
public field, so this is a minor release; the JSON wire format stays at
schema version 1 and old snapshots still parse.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@caniko

caniko commented Nov 15, 2026

Copy link
Copy Markdown
Owner Author

Closing unmerged at the operator's direction: secret expiry folds into the hub-ready campaign (hub renewals + notifications, secret-manager RotationGuide, canix Rotations.pkl) instead of a second expiry system in the fleet snapshot. The branch feat/secret-expiry stays for reference: its fail-closed assessment rules and tests are a reusable spec for the never-expires state and provider-reported expiry.

@caniko caniko closed this Nov 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant