Vehicle Admin improvements
This commit is contained in:
@@ -9,7 +9,7 @@
|
||||
1. **Wire dropdown API to refreshed data**
|
||||
- Run `make migrate` (or `npm run migrate:all` inside backend container) to ensure the new schema exists.
|
||||
- Execute the loader (see command below) so Postgres has the latest lookup entries.
|
||||
- Verify `VehicleDataRepository` queries and Redis caching logic continue to function against the reinstated tables.
|
||||
- Verify both the platform dropdown queries and the admin catalog APIs surface the same data set (admin APIs now read directly from `vehicles.*` tables).
|
||||
2. **Add Makefile wrapper**
|
||||
- Create a `make load-vehicle-data` task that shells into the backend container, installs `psycopg` if needed, and invokes `python3 scripts/load_vehicle_data.py` with the correct DB credentials and data directory.
|
||||
|
||||
@@ -25,3 +25,7 @@ python3 scripts/load_vehicle_data.py \
|
||||
```
|
||||
|
||||
> Run the command from the repository root (outside of containers) while `mvp-postgres` is up. Adjust host/port if executing inside a container.
|
||||
|
||||
## 2025-11-07 Update
|
||||
- Admin catalog CRUD endpoints have been refactored to read/write the normalized `vehicles.*` tables instead of the legacy `vehicle_dropdown_cache`.
|
||||
- Platform cache invalidation now happens immediately after each catalog mutation so both the admin UI and the user dropdown APIs stay in sync.
|
||||
|
||||
Reference in New Issue
Block a user