Project

Profile

Help

Story #7822

As a user, I can remove a Pulp plugin

Added by jsherril@redhat.com 12 months ago. Updated 6 days ago.

Status:
POST
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Katello
Sprint:
Sprint 108
Quarter:

Description

Motivation

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

Deliverables

  • 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

History

#1 Updated by ggainey 12 months ago

  • Tracker changed from Issue to Story
  • Project changed from Pulp to Migration Plugin
  • % Done set to 0
  • Severity deleted (2. Medium)
  • Triaged deleted (No)

#2 Updated by ttereshc 11 months ago

  • 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)

#3 Updated by ttereshc 11 months ago

Brought it back to the Pulp tracker, since on the pulpcore meetings we agreed that it makes sense to find a general solution.

#4 Updated by bmbouter 11 months ago

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?

#5 Updated by ttereshc 4 months ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ttereshc
  • Sprint set to Sprint 99

#6 Updated by pulpbot 4 months ago

  • Status changed from ASSIGNED to POST

#7 Updated by rchan 4 months ago

  • Sprint changed from Sprint 99 to Sprint 100

#8 Updated by rchan 3 months ago

  • Sprint changed from Sprint 100 to Sprint 101

#9 Updated by ipanova@redhat.com 3 months ago

  • Sprint changed from Sprint 101 to Sprint 102

#10 Updated by rchan 3 months ago

  • Sprint changed from Sprint 102 to Sprint 103

#11 Updated by rchan 2 months ago

  • Sprint changed from Sprint 103 to Sprint 104

#12 Updated by rchan about 2 months ago

  • Sprint changed from Sprint 104 to Sprint 105

#13 Updated by rchan about 1 month ago

  • Sprint changed from Sprint 105 to Sprint 106

#14 Updated by rchan 19 days ago

  • Sprint changed from Sprint 106 to Sprint 107

#15 Updated by rchan 6 days ago

  • Sprint changed from Sprint 107 to Sprint 108

Please register to edit this issue

Also available in: Atom PDF