## Summary - normalize provider-neutral target-scope and identity contracts across provider connection resolution, operation-start gating, verification reporting, and boundary configuration - align provider connection resource, onboarding, tenant summaries, and operation follow-up on the same shared scope contract while keeping Microsoft-specific profile details in provider-owned metadata - add Spec 281 artifacts and focused feature/browser coverage for the new provider-scope contract - move the tenant dashboard context-chip rail into Filament header widgets so the metadata row renders directly under the page subtitle ## Validation - `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Providers/ProviderConnectionTargetScopeNeutralityTest.php tests/Feature/Providers/ProviderIdentityResolutionNeutralityTest.php tests/Feature/Providers/ProviderOperationStartGateTargetScopeContextTest.php tests/Feature/Filament/ProviderConnectionResourceScopeSummaryTest.php tests/Feature/Onboarding/ManagedTenantOnboardingProviderConnectionScopeTest.php tests/Feature/Guards/ProviderConnectionMicrosoftScopeLeakGuardTest.php` - `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Browser/Spec281ProviderConnectionScopeSmokeTest.php` - `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Dashboard/TenantDashboardProductizationSummaryTest.php` - `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Browser/Dashboard/TenantDashboardProductizationSmokeTest.php` - `cd apps/platform && ./vendor/bin/sail bin pint --dirty --format agent` ## Notes - Filament remains on v5 with Livewire v4-compatible surfaces only. - Provider registration location is unchanged; Laravel 11+ providers stay in `apps/platform/bootstrap/providers.php`. - `ProviderConnectionResource` remains non-globally-searchable and still exposes View/Edit pages. - No new asset registration was added; deploy-time `filament:assets` expectations are unchanged. - No new destructive action path was introduced; existing server authorization and confirmation handling remain in place where applicable. Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #339
37 lines
1.2 KiB
PHP
37 lines
1.2 KiB
PHP
<?php
|
|
|
|
declare(strict_types=1);
|
|
|
|
it('keeps Microsoft-shaped provider scope out of shared provider platform-core contracts', function (): void {
|
|
$root = base_path();
|
|
|
|
$forbiddenByPath = [
|
|
'app/Services/Providers/ProviderIdentityResolution.php' => [
|
|
'tenantContext',
|
|
'target_scope.entra_tenant_id',
|
|
],
|
|
'app/Services/Providers/ProviderIdentityResolver.php' => [
|
|
'tenantContext',
|
|
],
|
|
'app/Services/Providers/PlatformProviderIdentityResolver.php' => [
|
|
'tenantContext',
|
|
],
|
|
'app/Services/Providers/ProviderOperationStartGate.php' => [
|
|
"'entra_tenant_id' =>",
|
|
'target_scope.entra_tenant_id',
|
|
],
|
|
'config/provider_boundaries.php' => [
|
|
'target_scope.entra_tenant_id',
|
|
],
|
|
];
|
|
|
|
foreach ($forbiddenByPath as $relativePath => $fragments) {
|
|
$contents = (string) file_get_contents($root.'/'.$relativePath);
|
|
|
|
foreach ($fragments as $fragment) {
|
|
expect($contents)
|
|
->not->toContain($fragment, sprintf('%s still exposes [%s] as shared provider-scope truth.', $relativePath, $fragment));
|
|
}
|
|
}
|
|
});
|