ahmido
1f3619bd16
## Summary - introduce a shared tenant-owned query and record-resolution canon for first-slice Filament resources - harden direct views, row actions, bulk actions, relation managers, and workspace-admin canonical viewers against wrong-tenant access - add registry-backed rollout metadata, search posture handling, architectural guards, and focused Pest coverage for scope parity and 404/403 semantics ## Included - Spec 150 package under `specs/150-tenant-owned-query-canon-and-wrong-tenant-guards/` - shared support classes: `TenantOwnedModelFamilies`, `TenantOwnedQueryScope`, `TenantOwnedRecordResolver` - shared Filament concern: `InteractsWithTenantOwnedRecords` - resource/page/policy hardening across findings, policies, policy versions, backup schedules, backup sets, restore runs, inventory items, and Entra groups - additional regression coverage for canonical tenant state, wrong-tenant record resolution, relation-manager congruence, and action-surface guardrails ## Validation - `vendor/bin/sail artisan test --compact` passed - full suite result: `2733 passed, 8 skipped` - formatting applied with `vendor/bin/sail bin pint --dirty --format agent` ## Notes - Livewire v4.0+ compliant via existing Filament v5 stack - provider registration remains in `bootstrap/providers.php` - globally searchable first-slice posture: Entra groups scoped; policies and policy versions explicitly disabled - destructive actions continue to use confirmation and policy authorization - no new Filament assets added; existing deployment flow remains unchanged, including `php artisan filament:assets` when registered assets are used Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #180
73 lines
2.3 KiB
PHP
73 lines
2.3 KiB
PHP
<?php
|
|
|
|
declare(strict_types=1);
|
|
|
|
namespace App\Filament\Concerns;
|
|
|
|
use App\Models\Tenant;
|
|
use App\Support\WorkspaceIsolation\TenantOwnedQueryScope;
|
|
use App\Support\WorkspaceIsolation\TenantOwnedRecordResolver;
|
|
use Illuminate\Database\Eloquent\Builder;
|
|
use Illuminate\Database\Eloquent\Model;
|
|
|
|
trait InteractsWithTenantOwnedRecords
|
|
{
|
|
protected static function tenantOwnedRelationshipName(): string
|
|
{
|
|
$relationshipName = property_exists(static::class, 'tenantOwnershipRelationshipName')
|
|
? static::$tenantOwnershipRelationshipName
|
|
: null;
|
|
|
|
return is_string($relationshipName) && $relationshipName !== ''
|
|
? $relationshipName
|
|
: 'tenant';
|
|
}
|
|
|
|
protected static function resolveTenantContextForTenantOwnedRecords(): ?Tenant
|
|
{
|
|
if (method_exists(static::class, 'resolveTenantContextForCurrentPanel')) {
|
|
return static::resolveTenantContextForCurrentPanel();
|
|
}
|
|
|
|
if (method_exists(static::class, 'panelTenantContext')) {
|
|
return static::panelTenantContext();
|
|
}
|
|
|
|
return null;
|
|
}
|
|
|
|
public static function getTenantOwnedEloquentQuery(): Builder
|
|
{
|
|
return static::scopeTenantOwnedQuery(parent::getEloquentQuery());
|
|
}
|
|
|
|
protected static function scopeTenantOwnedQuery(Builder $query, ?Tenant $tenant = null): Builder
|
|
{
|
|
return app(TenantOwnedQueryScope::class)->apply(
|
|
$query,
|
|
$tenant ?? static::resolveTenantContextForTenantOwnedRecords(),
|
|
static::tenantOwnedRelationshipName(),
|
|
);
|
|
}
|
|
|
|
protected static function resolveTenantOwnedRecord(Model|int|string|null $record, ?Builder $query = null, ?Tenant $tenant = null): ?Model
|
|
{
|
|
$scopedQuery = static::scopeTenantOwnedQuery(
|
|
$query ?? parent::getEloquentQuery(),
|
|
$tenant,
|
|
);
|
|
|
|
return app(TenantOwnedRecordResolver::class)->resolve($scopedQuery, $record);
|
|
}
|
|
|
|
protected static function resolveTenantOwnedRecordOrFail(Model|int|string|null $record, ?Builder $query = null, ?Tenant $tenant = null): Model
|
|
{
|
|
$scopedQuery = static::scopeTenantOwnedQuery(
|
|
$query ?? parent::getEloquentQuery(),
|
|
$tenant,
|
|
);
|
|
|
|
return app(TenantOwnedRecordResolver::class)->resolveOrFail($scopedQuery, $record);
|
|
}
|
|
}
|