Repository navigation
Record an audit log of key and deletion actions - #365
Merged
Merged
Conversation
A shared server had no record of who created or revoked API keys, deleted traces or purged them. Migration 6 adds an audit_events table in both stores, written in the same transaction as each action: API keys created and revoked, traces deleted, and retention purges that removed traces, with project, target, counts and the acting identity. Admins read it through GET /v1/audit-events, AgentLoopClient.list_audit_events and the audit-log and remote-audit-log commands. Key values are never recorded. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
AgentLoop replay self-testThis required repository check evaluates generated synthetic demo traces. It tests the replay and CI machinery; it does not show that this PR improves application performance. AgentLoop CI Report
Performance Gates
Trace inputsThis comparison includes synthetic data. It does not establish application performance gains from a pull request.
Metric Impact
Top Findings
|
The Postgres fixtures truncated every table except the new audit_events, so events from earlier tests leaked into the audit-log test. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
A shared server now has security-relevant actions (key creation/revocation, trace deletion, retention purges) but kept no record of who did them.
Tests: store contract (both backends in CI) incl. ordering, no-op actions, project filter and no secrets; API admin-only access and actors; CLI; client URL/header scope; migration version sets updated. 246 related tests pass locally. Docs: PRODUCTION (Audit log), CLOUD_DEPLOY, API_VERSIONING, changelog.
🤖 Generated with Claude Code