feat(007): device config & compliance snapshot/restore improvements #9
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "feat/007-device-config-compliance"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Captures Compliance notifications for deviceCompliancePolicy via Graph $expand=scheduledActionsForRule($expand=scheduledActionConfigurations) (direct navigation endpoint returns 400).
Cleans up Policy Version UI: renders Assignments + Compliance notifications as separate Filament sections/cards (no “merged card” look); shows Default rule when ruleName is null.
Makes the Diff tab admin-readable by diffing normalized + flattened keys, hiding noisy @odata.context / large nested payloads, and summarizing compliance notifications as template IDs (advanced raw diff remains available).
Why
Graph .../scheduledActionsForRule is unreliable (No OData route exists...), but $expand works (validated in Graph Explorer).
Raw JSON diffs were too noisy and unusable for admins.
Testing
./vendor/bin/pint --dirty
PolicyVersionViewAssignmentsTest.php
fix(007): make policy version diffs readableto feat(007): device config & compliance snapshot/restorefeat(007): device config & compliance snapshot/restoreto feat(007): device config & compliance snapshot/restore improvementsCompliance Policies: Snapshot/Normalizer verbessert, inkl. Compliance Notifications (scheduled actions) und besser lesbarem Normalized Diff
Restore: Preview/Results zeigen Compliance‑Mapping + Warnung bei fehlenden Notification Templates
Graph contracts: Query/$select/$expand sicherer sanitizen
Tests aktualisiert/ergänzt (Restore Preview/Execution, Policy Version View, Normalizer, Contract Registry)