Reconcile uncertain delivery and invalidate orphan credentials #23
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#23
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
Resolve missing OpenBao acknowledgements without redelivering secrets or destroying credentials that belong to committed leases.
Delivery class
agent-unit— implementsrc/reconcile.rsagainst captured OpenBao lease-state fixtures.Design
Compare operation and token IDs with committed lease metadata. Recover acknowledgement for a match. Mark a missing or mismatched lease token orphaned, invalidate it by exact token ID, and require a new operation ID before replacement. Partial invalidation remains visible and retryable.
Tasks
delivery_uncertainselection.Specification Delta
Requirement: acknowledgement loss is not evidence of lease loss
Scenario: OpenBao committed but its acknowledgement was lost
OpenSpec
OpenSpec 20
Structural parent
Vedanta#20
larandar referenced this issue2026-09-02 19:23:32 +00:00