The registry database was seeded once in migration V2 and never updated since. The ai and packaging categories were added to catalog-overrides.json later but no corresponding Flyway migration was added to the registry. And when platform catalogs are ingested via the admin endpoint, the code does Category.findByKey(id).ifPresent(...) — so ai and packaging categories from the platform descriptor are silently dropped because they don't exist in the category table.
The table also has grpc and integration categories that aren't in the platform overrides.
One fix would be a new migration (V20) in registry.quarkus.io to insert the missing ai and packaging categories. However, this seems tactical, and we'd have this problem every time we change categories. So I think maybe being DRYer and treating the catalog-overrides as a single source of truth is better.
The registry database was seeded once in migration V2 and never updated since. The ai and packaging categories were added to catalog-overrides.json later but no corresponding Flyway migration was added to the registry. And when platform catalogs are ingested via the admin endpoint, the code does Category.findByKey(id).ifPresent(...) — so ai and packaging categories from the platform descriptor are silently dropped because they don't exist in the category table.
The table also has
grpcandintegrationcategories that aren't in the platform overrides.One fix would be a new migration (V20) in registry.quarkus.io to insert the missing ai and packaging categories. However, this seems tactical, and we'd have this problem every time we change categories. So I think maybe being DRYer and treating the catalog-overrides as a single source of truth is better.