This is an update of catalogs, with Jan's feedback incorporated.
I did not add a migration for legacy users, so you'll need to re-do your database
before adding CatalogEntries, and existing SuggestedDeployables will stop working. I
started to add a migration to "do the right thing," but I don't think it
will work. The problem is that a CatalogEntry now needs to belong to a Catalog, which
needs to belong to a Pool. To do this programmatically, we'd have to detect if there
were SuggestedDeployables (which become CatalogEntries), create a Catalog, and then
arbitrarily tie that Catalog to some pool. (Plus, you can't 'down' the
migration, since you'd end up deleting data.) It ended up feeling really messy and
arbitrary. If there are strong objections I can add it, but I'm not sure it's
advisable.
-- Matt
Show replies by date