## Why
Some Microsoft Graph / Intune identifiers are not UUIDs (e.g. scope tag id "0"). With `inventory_links.source_id` / `target_id` typed as `uuid`, PostgreSQL fails when inventory dependency extraction tries to persist those edges.
## What
- PostgreSQL migration changes `inventory_links.source_id` and `inventory_links.target_id` to `text`.
- Regression test ensures a non-UUID id ("0") can be persisted; on pgsql it also asserts the columns are `text`.
## Notes
- UUID identifiers continue to work (stored as strings).
- No UI/Filament changes.
## Testing
- `vendor/bin/sail artisan test --compact tests/Feature/Inventory/InventoryLinksNonUuidIdsTest.php`
Co-authored-by: Ahmed Darrazi <ahmeddarrazi@MacBookPro.fritz.box>
Reviewed-on: #96
575 B
575 B
Tasks: Inventory links support non-UUID IDs
Phase 1: Spec + setup
- T001 Create spec folder and docs
Phase 2: Tests (TDD)
- T002 Add pgsql schema regression test in
tests/Feature/Inventory/InventoryLinksNonUuidIdsTest.php
Phase 3: Implementation
- T003 Add migration to change
inventory_links.source_id+target_idtotexton PostgreSQL
Phase 4: Validation
- T004 Run tests:
vendor/bin/sail artisan test --compact tests/Feature/Inventory/InventoryLinksNonUuidIdsTest.php - T005 Run Pint:
vendor/bin/sail bin pint --dirty