Implement OpenBao lease read, rotation, and revocation transitions #24
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Meta/Campaign
Meta/Epic
Meta/Session
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Curated
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Scope/Campaign
Status/Abandoned
Status/Blocked
Status/Conflicted
Status/In Progress
Status/In Review
Status/Need Grooming
Status/Need More Info
Status/Ready
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
Reference
Ting/Vedanta#24
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Proposal
Implement the non-issue OpenBao lease state machine after initial authorization and delivery exist.
Delivery class
agent-unit— implementopenbao-plugin/src/lease.rswith deterministic state-machine tests.Design
Read returns metadata only. Rotation re-evaluates the active grant, retains the lease ID, and creates a distinct successor token and generation. Revoke denies further lease use immediately and remains
revocation_pendinguntil every downstream token invalidation completes.Tasks
ReadLease.RotateLeasewith grant re-evaluation.RevokeLeaseand pending downstream invalidation state.Specification Delta
Requirement: lease transitions never recover an old secret
Scenario: a caller reads or retries an existing lease
OpenSpec
OpenSpec 20
Structural parent
Vedanta#20
larandar referenced this issue2026-09-02 19:23:32 +00:00