Summary Consolidates the “Tenant Operate Hub” work (Spec 085) and the follow-up adjustments from the 086 session merge into a single branch ready to merge into dev. Primary focus: stabilize Ops/Operate Hub UX flows, tighten/align authorization semantics, and make the full Sail test suite green. Key Changes Ops UX / Verification Readonly members can view verification operation runs (reports) while starting verification remains restricted. Normalized failure reason-code handling and aligned UX expectations with the provider reason-code taxonomy. Onboarding wizard UX “Start verification” CTA is hidden while a verification run is active; “Refresh” is shown during in-progress runs. Treats provider_permission_denied as a blocking reason (while keeping legacy compatibility). Test + fixture hardening Standardized use of default provider connection fixtures in tests where sync/restore flows require it. Fixed multiple Filament URL/tenant-context test cases to avoid 404s and reduce tenancy routing brittleness. Policy sync / restore safety Enrollment configuration type collision classification tests now exercise the real sync path (with required provider connection present). Restore edge-case safety tests updated to reflect current provider-connection requirements. Testing vendor/bin/sail artisan test --compact (green) vendor/bin/sail bin pint --dirty (green) Notes Includes merged 086 session work already (no separate PR needed). Co-authored-by: Ahmed Darrazi <ahmeddarrazi@ebc83aaa-d947-4a08-b88e-bd72ac9645f7.fritz.box> Co-authored-by: Ahmed Darrazi <ahmeddarrazi@MacBookPro.fritz.box> Co-authored-by: Ahmed Darrazi <ahmeddarrazi@adsmac.fritz.box> Reviewed-on: #103
40 lines
1.6 KiB
Markdown
40 lines
1.6 KiB
Markdown
# Quickstart: Tenant Operate Hub / Tenant Overview IA
|
|
|
|
**Date**: 2026-02-09
|
|
**Branch**: 085-tenant-operate-hub
|
|
|
|
## Local setup
|
|
|
|
- Start containers: `vendor/bin/sail up -d`
|
|
- Install deps (if needed): `vendor/bin/sail composer install`
|
|
|
|
## Manual verification steps (happy path)
|
|
|
|
1. Sign in.
|
|
2. Select a workspace (via the context bar).
|
|
3. Enter a tenant context (e.g., go to `/admin/t/{tenant}` via the tenant panel).
|
|
4. In the tenant panel sidebar, open the **Monitoring** group and click:
|
|
- Runs → lands on `/admin/operations`
|
|
5. Verify `/admin/operations` shows:
|
|
- Header scope: `Scope: Tenant — <tenant name>`
|
|
- CTAs: `Back to <tenant name>` and `Show all tenants`
|
|
- The table default scope is tenant-filtered to the active tenant.
|
|
6. Click `Show all tenants`.
|
|
7. Verify you stay on `/admin/operations` and scope becomes `Scope: Workspace — all tenants`.
|
|
8. Open an operation run detail at `/admin/operations/{run}`.
|
|
9. Verify the header shows:
|
|
- `← Back to <tenant name>`
|
|
- secondary `Show all operations` → `/admin/operations`
|
|
10. Click `← Back to <tenant name>` and verify it lands on the tenant dashboard (`/admin/t/{tenant}`).
|
|
|
|
## Negative verification (security)
|
|
|
|
- With tenant context active, revoke tenant entitlement for the test user.
|
|
- Reload `/admin/operations`.
|
|
- Verify scope is workspace-wide and no tenant name / “Back to tenant” affordance appears.
|
|
- Request the tenant dashboard URL directly (`/admin/t/{tenant}`) and verify deny-as-not-found.
|
|
|
|
## Test commands (to be added in Phase 2)
|
|
|
|
- Targeted suite: `vendor/bin/sail artisan test --compact --filter=OperationsIndexScopeTest`
|