[Task] Wave 0 audit trace context for admin and module operations #1

Closed
opened 2026-07-08 20:44:04 +02:00 by zemion · 1 comment
Owner

Goal

Expose enough audit trace context for operators to understand module/package changes, policy decisions, and administrative actions.

Scope

  • Standardize event/request/run correlation fields for admin module operations.
  • Capture actor, tenant/scope, request id, module id, run id, and outcome where available.
  • Provide a UI/API shape that admin and ops views can link to without importing audit internals.
  • Document retention and redaction expectations for operational audit details.

Acceptance Criteria

  • Module install/update/uninstall plans and rollbacks can be traced to an actor and run id.
  • Policy/admin changes can be inspected with a readable context summary.
  • Audit context degrades gracefully when optional modules are not installed.
  • Tests cover trace payload shape and redaction-sensitive fields.
  • Wave 0 platform hardening.
  • Admin preflight/rollback visibility and ops health/deployment profile issues.
## Goal Expose enough audit trace context for operators to understand module/package changes, policy decisions, and administrative actions. ## Scope - Standardize event/request/run correlation fields for admin module operations. - Capture actor, tenant/scope, request id, module id, run id, and outcome where available. - Provide a UI/API shape that admin and ops views can link to without importing audit internals. - Document retention and redaction expectations for operational audit details. ## Acceptance Criteria - Module install/update/uninstall plans and rollbacks can be traced to an actor and run id. - Policy/admin changes can be inspected with a readable context summary. - Audit context degrades gracefully when optional modules are not installed. - Tests cover trace payload shape and redaction-sensitive fields. ## Related - Wave 0 platform hardening. - Admin preflight/rollback visibility and ops health/deployment profile issues.
Author
Owner

Implemented and verified.

  • Added core audit_operation_context for module/admin lifecycle details: module_id, request_id, run_id, outcome, _trace, and sanitized extras.
  • Admin module lifecycle routes now use the shared context for queued/cancelled/retried/planned/applied events.
  • Added govoplan-audit/docs/AUDIT_TRACE_CONTEXT.md and README linkage.
  • Tests cover trace payload shape and redaction-sensitive fields in tests/test_core_events.py.
Implemented and verified. - Added core `audit_operation_context` for module/admin lifecycle details: `module_id`, `request_id`, `run_id`, `outcome`, `_trace`, and sanitized extras. - Admin module lifecycle routes now use the shared context for queued/cancelled/retried/planned/applied events. - Added `govoplan-audit/docs/AUDIT_TRACE_CONTEXT.md` and README linkage. - Tests cover trace payload shape and redaction-sensitive fields in `tests/test_core_events.py`.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: add-ideas/govoplan-audit#1
No description provided.