926264c8d1
- Add modal toggle include_dependencies (default on)\n- Persist into selection payload deterministically\n- Update quickstart, tasks, and tests
37 lines
1.3 KiB
Markdown
37 lines
1.3 KiB
Markdown
# Quickstart: Inventory Sync Button (046)
|
|
|
|
## Goal
|
|
Start an Inventory Sync for the currently selected tenant from the Filament UI, observe progress in:
|
|
- Filament database notifications panel
|
|
- Bottom-right progress widget (BulkOperationProgress)
|
|
|
|
## Local prerequisites
|
|
- Sail running
|
|
- Queue worker running (required for the new queued sync job)
|
|
|
|
## Run locally
|
|
|
|
1. Start the stack:
|
|
- `./vendor/bin/sail up -d`
|
|
|
|
2. Run a queue worker:
|
|
- `./vendor/bin/sail artisan queue:work --tries=1`
|
|
|
|
3. Open the admin panel and pick a tenant:
|
|
- Visit `/admin` and select a tenant context.
|
|
|
|
4. Navigate to Inventory:
|
|
- Use the left navigation “Inventory”.
|
|
|
|
5. Click “Run Inventory Sync”:
|
|
- Select which policy types to include (or click “Select all”).
|
|
- (Optional) Toggle “Include dependencies” if you want dependency extraction where supported.
|
|
- You should see:
|
|
- A database notification (started)
|
|
- A bottom-right progress widget entry for `Sync inventory`
|
|
- A new Inventory Sync Run record in the Inventory Sync Runs list
|
|
|
|
## Notes
|
|
- If the queue worker is not running, the progress widget will remain in “Queued…” and the run will not advance.
|
|
- Concurrency/lock gating may skip the run; the UI should show a clear informational message and a run record will reflect the skip reason.
|