## Summary - add the Spec 180 tenant backup-health resolver and value objects to derive absent, stale, degraded, healthy, and schedule-follow-up posture from existing backup and schedule truth - surface backup posture and reason-driven drillthroughs in the tenant dashboard and preserve continuity on backup-set and backup-schedule destinations - add deterministic local/testing browser-fixture seeding plus a local fixture-login helper for the blocked drillthrough `403` scenario, along with the related spec artifacts and focused regression coverage ## Testing - `vendor/bin/sail artisan test --compact tests/Feature/Auth/BackupHealthBrowserFixtureLoginTest.php tests/Feature/Console/TenantpilotSeedBackupHealthBrowserFixtureCommandTest.php` - `vendor/bin/sail artisan test --compact tests/Unit/Support/BackupHealth/TenantBackupHealthResolverTest.php tests/Feature/Filament/DashboardKpisWidgetTest.php tests/Feature/Filament/NeedsAttentionWidgetTest.php tests/Feature/Filament/TenantDashboardTruthAlignmentTest.php tests/Feature/Filament/TenantDashboardTenantScopeTest.php tests/Feature/Filament/TenantDashboardDbOnlyTest.php tests/Feature/Filament/BackupSetListContinuityTest.php tests/Feature/Filament/BackupSetEnterpriseDetailPageTest.php tests/Feature/BackupScheduling/BackupScheduleLifecycleTest.php tests/Feature/Auth/BackupHealthBrowserFixtureLoginTest.php tests/Feature/Console/TenantpilotSeedBackupHealthBrowserFixtureCommandTest.php` ## Notes - Filament v5 / Livewire v4 compliant; no panel-provider change was needed, so `bootstrap/providers.php` remains unchanged - no new globally searchable resource was introduced, so global-search behavior is unchanged - no new destructive action was added; existing destructive actions and confirmation behavior remain unchanged - no new asset registration was added; the existing deploy-time `php artisan filament:assets` step remains sufficient - the local fixture login helper route is limited to `local` and `testing` environments - the focused and broader Spec 180 packs are green; the full suite was not rerun after these changes Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #212
61 lines
1.8 KiB
PHP
61 lines
1.8 KiB
PHP
<?php
|
|
|
|
declare(strict_types=1);
|
|
|
|
namespace App\Support\BackupHealth;
|
|
|
|
use App\Support\BackupQuality\BackupQualitySummary;
|
|
use Carbon\CarbonInterface;
|
|
|
|
final readonly class TenantBackupHealthAssessment
|
|
{
|
|
public const POSTURE_ABSENT = 'absent';
|
|
|
|
public const POSTURE_STALE = 'stale';
|
|
|
|
public const POSTURE_DEGRADED = 'degraded';
|
|
|
|
public const POSTURE_HEALTHY = 'healthy';
|
|
|
|
public const REASON_NO_BACKUP_BASIS = 'no_backup_basis';
|
|
|
|
public const REASON_LATEST_BACKUP_STALE = 'latest_backup_stale';
|
|
|
|
public const REASON_LATEST_BACKUP_DEGRADED = 'latest_backup_degraded';
|
|
|
|
public const REASON_SCHEDULE_FOLLOW_UP = 'schedule_follow_up';
|
|
|
|
public function __construct(
|
|
public int $tenantId,
|
|
public string $posture,
|
|
public ?string $primaryReason,
|
|
public string $headline,
|
|
public ?string $supportingMessage,
|
|
public ?int $latestRelevantBackupSetId,
|
|
public ?CarbonInterface $latestRelevantCompletedAt,
|
|
public ?BackupQualitySummary $qualitySummary,
|
|
public BackupFreshnessEvaluation $freshnessEvaluation,
|
|
public BackupScheduleFollowUpEvaluation $scheduleFollowUp,
|
|
public bool $healthyClaimAllowed,
|
|
public ?BackupHealthActionTarget $primaryActionTarget,
|
|
public string $positiveClaimBoundary,
|
|
) {}
|
|
|
|
public function hasActiveReason(): bool
|
|
{
|
|
return $this->primaryReason !== null;
|
|
}
|
|
|
|
public function tone(): string
|
|
{
|
|
return match ($this->primaryReason ?? $this->posture) {
|
|
self::REASON_NO_BACKUP_BASIS => 'danger',
|
|
self::REASON_LATEST_BACKUP_STALE => 'warning',
|
|
self::REASON_LATEST_BACKUP_DEGRADED => 'warning',
|
|
self::REASON_SCHEDULE_FOLLOW_UP => 'warning',
|
|
self::POSTURE_HEALTHY => 'success',
|
|
default => 'gray',
|
|
};
|
|
}
|
|
}
|