As a user, I can remove a Pulp plugin
There are cases when a user might want to remove a plugin:
- plugin is no longer in use but it's data in the db is quite large (pulp-2to3-migration case)
- incompatible plugins
- all plugin related data should be removed from the DB, its schema as well
- artifacts can be left for orphan cleanup, don't need to be removed immediately
- it should be possible to install this plugin back again, make sure django migrations are applied in this case accordingly
Original request from Katello¶
After a pulp2 to 3 migration, the left over migration data is quite large and needs to be cleaned up. there needs to be a command or api to clean it up.
In addition we need a way/instructions to remove the plugin altogether and delete its added schema entirely
- Tracker changed from Issue to Story
- Project changed from Pulp to Migration Plugin
- % Done set to 0
- Severity deleted (
- Triaged deleted (
- Project changed from Migration Plugin to Pulp
- Subject changed from provide command or other way to remove migration db data to As a user, I can remove a Pulp plugin
- Description updated (diff)
Brought it back to the Pulp tracker, since on the pulpcore meetings we agreed that it makes sense to find a general solution.
I asked in #django and was told there is no pre-built way to do this. So I imagine we'll ship a custom command.
Is there a programmatic way to identify all the tables brought in by a django app by it's django app name?
- Status changed from NEW to ASSIGNED
- Assignee set to ttereshc
- Sprint set to Sprint 99
- Status changed from ASSIGNED to POST
- Sprint changed from Sprint 99 to Sprint 100
- Sprint changed from Sprint 100 to Sprint 101
- Sprint changed from Sprint 101 to Sprint 102
Please register to edit this issue
Also available in: Atom