Repository navigation
Conversation
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>
Owner
Author
|
Closing unmerged at the operator's direction: secret expiry folds into the hub-ready campaign (hub |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an optional
secretssection tofleetix::status::FleetStatusso 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,neverorunknown.neveris its own kind, distinct from undeclared, and never warns.SecretState: ok, expiring, expired, never, undeclared, unverifiable, invalid.assess_secretjudges against an explicitas_ofwith no I/O.attention()adds one per expiring, expired, invalid or unverifiable secret, plus one for an inventory error. Existing counts are unchanged.secrets: None.FleetStatusgained 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-targetsand treefmt are clean.Design: two Sol rounds (
openai/gpt-6.1-solxhigh) 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