ahmido a0ed9e24c5 feat: unify provider connection actions and notifications (#73 )

## Summary
- introduce the Provider Connection Filament resource (list/create/edit) with DB-only controls, grouped action dropdowns, and badge-driven status/health rendering
- wire up the provider foundation stack (migrations, models, policies, providers, operations, badges, and audits) plus the required spec docs/checklists
- standardize Inventory Sync notifications so the job no longer writes its own DB rows; terminal notifications now flow exclusively through OperationRunCompleted while the start surface still shows the queued toast

## Testing
- ./vendor/bin/sail php ./vendor/bin/pint --dirty
- ./vendor/bin/sail artisan test tests/Unit/Badges/ProviderConnectionBadgesTest.php
- ./vendor/bin/sail artisan test tests/Feature/ProviderConnections tests/Feature/Filament/ProviderConnectionsDbOnlyTest.php
- ./vendor/bin/sail artisan test tests/Feature/Inventory/RunInventorySyncJobTest.php tests/Feature/Inventory/InventorySyncStartSurfaceTest.php

Co-authored-by: Ahmed Darrazi <ahmeddarrazi@MacBookPro.fritz.box>
Reviewed-on: #73

2026-01-25 01:01:37 +00:00

1.6 KiB

Raw Permalink Blame History

Contracts: Graph Contract Registry Updates (Provider Foundation v1)

Branch: 061-provider-foundation
Date: 2026-01-24

Purpose

Provider foundation operations must not introduce ad-hoc Microsoft Graph endpoints. Any new Graph resources required by provider modules should be added to the central registry (config/graph_contracts.php) and consumed via GraphClientInterface.

Required additions (v1)

1) Connection health check

Operation: Provider connection health check (“ping”)
Graph call: GET /organization (basic org metadata)
Registry note: Ensure the org endpoint is modeled/approved in the contract registry (either as a first-class type or as an explicitly allowed internal call within the Graph client).

2) Compliance snapshot (counts)

Operation: Compliance snapshot (device compliance state counts)
Graph calls (one of the contract-approved patterns):

Option A: List managed devices with a minimal select and compute counts client-side.
- Resource: deviceManagement/managedDevices
- Required fields: id, complianceState
Option B: Use Graph count endpoints / filtered counts if supported reliably.
- Resource: deviceManagement/managedDevices/$count (with filters)

Registry note: Add a contract entry for managed devices (and any count strategy used) with allowed selects/filters to prevent accidental over-fetching.

Existing registry reuse

Provider inventory collection should prefer existing policy-type contracts already present in config/graph_contracts.php (e.g., Intune policy types and directory group listing), rather than introducing new “quick endpoints”.

1.6 KiB Raw Permalink Blame History