`scripts/migrations/019-set-parent-only-troves.py` talks to sfx database to select trove categories with `parent_only==1`, adn than sets `parent_only = True` on corresponding categories in Allura db. I wonder if we could drop this and use a hardcoded list of ids in new trove command (fetched once from sfx db) to avoid dependency on sfx. What do you think?
--- ** [tickets:#6848] Coalesce scripts/migrations/*trove*.py into command/create_trove_categories.py** **Status:** in-progress **Labels:** 42cc **Created:** Tue Nov 05, 2013 06:26 PM UTC by Dave Brondsema **Last Updated:** Wed Nov 06, 2013 07:52 PM UTC **Owner:** nobody command/create_trove_categories.py sets up the initial trove categories. Over time we've created several migrations to update the trove categories, but few (if any) of those changes are in the command/create_trove_categories.py So when you start a new instance of Allura, you don't have the latest (unless you run all the migrations). So we should take all the changes specified in these files, and update command/create_trove_categories.py to set them all up properly there. Be very careful! :) scripts/migrations/014-add-trove-category-agpl.py scripts/migrations/016-add-trove-category-lppl.py scripts/migrations/017-sync-trove-categories.py scripts/migrations/019-set-parent-only-troves.py scripts/migrations/021-add-new-trove-license-categories.py scripts/migrations/023-add-new-trove-license-category.py scripts/migrations/030-set-trove-show_as_skill.py The end result should be that the `trove_category` collection is the same after running NEW command/create_trove_categories.py, compared to OLD command/create_trove_categories.py PLUS all migrations. --- Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
