Repository navigation
fix(policy): reject concurrent and non-active key rotations - #4200
Conversation
Signed-off-by: Chris Reed <creed@virtru.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
Benchmark results, click to expandBulk Benchmark Results
TDF3 Benchmark Results
|
Signed-off-by: Chris Reed <creed@virtru.com>
Benchmark results, click to expandBulk Benchmark Results
TDF3 Benchmark Results
|
Signed-off-by: Chris Reed <creed@virtru.com>
Benchmark results, click to expandBulk Benchmark Results
TDF3 Benchmark Results
|
Signed-off-by: Chris Reed <creed@virtru.com>
Benchmark results, click to expandBulk Benchmark Results
TDF3 Benchmark Results
|
Signed-off-by: Chris Reed <creed@virtru.com>
Benchmark results, click to expandBulk Benchmark Results
TDF3 Benchmark Results
|
Signed-off-by: Chris Reed <creed@virtru.com>
Benchmark results, click to expandBulk Benchmark Results
TDF3 Benchmark Results
|
|
Proposed Changes
Require an ACTIVE source before key rotation, returning a logged
FailedPreconditionerror (key must be ACTIVE). Atomically enforce that status when updating the source so concurrent requests produce one successor; a stale request returns the existingNotFounderror. Preserve key metadata and mapping/base-key transfers.Checklist
Testing Instructions
Race-enabled tests verify non-base-key rotation, rejection of a rotated source, and a single concurrent successor with no loser record. All 13 CLI rotation BATS cases pass, including the early error and backend logging. Focused unit tests and diff lint pass. Full checks encounter existing lint/vulnerability findings and a round-trip suite requiring a separately provisioned platform.
Summary by CodeRabbit