fa/breadcrumb-the-shire
1
0
Fork 1
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

fix(user-lifecycle): track last-run state in core, not in audit log

Browse Source 
The "Last run" KPI tile stayed empty after a manual policy run, even
though the run completed successfully. Two distinct bugs were
involved:

1. The dashboard read latestSystemRun() from the audit log filtered by
   trigger_type='system'. UserLifecycleService::run() never sets that
   value — it uses 'manual' for actor-triggered runs and 'cron' for
   scheduled ones. The query never matched anything.

2. Even with the right trigger_type, the audit log only writes per-user
   entries (logDeactivate / logDelete / logDeleteFailure). A run that
   processes zero users — including most cron ticks on a healthy
   tenant — leaves no trace, so the tile would still show "—" after a
   correct execution.

Both bugs share one root cause: run-trigger state was being inferred
from audit-log details, but those are two semantically different
things. Audit log answers "what did the run do?". A "last run" tile
answers "did the run happen?".

This commit moves run-trigger state to the core settings table and
keeps the audit log strictly for per-user events:

* Two new keys in core/Service/Settings/SettingKeys —
  USER_LIFECYCLE_LAST_RUN_AT_KEY and USER_LIFECYCLE_LAST_RUN_STATUS_KEY.
* SettingsUserLifecycleGateway gains recordLastRun() and getLastRun().
  UserSettingsGateway exposes them as recordLifecycleLastRun() /
  getLifecycleLastRun() so UserLifecycleService can call through its
  existing dependency without growing its constructor.
* UserLifecycleService::run() writes both keys in finally — every time
  the lock was acquired, regardless of whether any user was processed
  and regardless of whether the run finished cleanly. Status reflects
  $result['ok'] ('success' / 'failed').
* UserLifecyclePolicyDashboardService gains a lastRun() reader. Action
  page now sources the KPI tile from this core service instead of the
  audit interface — so the tile works even when the audit module is
  disabled.
* The audit-side lastRun() / latestSystemRun() / their tests are
  removed (YAGNI). Phase 4 (activity feed) can rebuild from the audit
  filter grid without a special method.

Behaviorally: a no-op run now records "Last run: just now · ✓ Success"
in the cockpit, exactly as expected.

All six quality gates green.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Felix Schneider
2026-04-26 21:07:57 +02:00
parent 97d09fbd94
commit 06118c1b26
13 changed files with 126 additions and 92 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
modules/audit/tests/Module/Audit/Service/UserLifecycleAuditDashboardServiceTest.php
View File

@@ -8,34 +8,6 @@ use PHPUnit\Framework\TestCase;
class UserLifecycleAuditDashboardServiceTest extends TestCase
{
public function testLastRunReturnsNullWhenRepositoryHasNoSystemRun(): void
{
$repository = $this->createMock(UserLifecycleAuditRepository::class);
$repository->expects($this->once())->method('latestSystemRun')->willReturn(null);
$service = new UserLifecycleAuditDashboardService($repository);
$this->assertNull($service->lastRun());
}
public function testLastRunNormalizesRowToContractShape(): void
{
$repository = $this->createMock(UserLifecycleAuditRepository::class);
$repository->method('latestSystemRun')->willReturn([
'created_at' => '2026-04-25 12:00:00',
'status' => 'success',
'action' => 'deactivate',
]);
$service = new UserLifecycleAuditDashboardService($repository);
$row = $service->lastRun();
$this->assertIsArray($row);
$this->assertSame('2026-04-25 12:00:00', $row['created_at']);
$this->assertSame('success', $row['status']);
$this->assertSame('deactivate', $row['action']);
}
public function testActionCountInWindowReturnsZeroForUnknownAction(): void
{
$repository = $this->createMock(UserLifecycleAuditRepository::class);