Project

Profile

Help

Story #7822

closed

As a user, I can remove a Pulp plugin

Added by jsherril@redhat.com about 2 years ago. Updated about 1 year ago.

Status:
CLOSED - DUPLICATE
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 112
Quarter:

Description

Ticket moved to GitHub: "pulp/pulpcore/1945":https://github.com/pulp/pulpcore/issues/1945


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

Actions #1

Updated by ggainey about 2 years 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)
Actions #2

Updated by ttereshc about 2 years 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)
Actions #3

Updated by ttereshc about 2 years ago

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

Actions #4

Updated by bmbouter about 2 years 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?

Actions #5

Updated by ttereshc over 1 year ago

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

Updated by pulpbot over 1 year ago

  • Status changed from ASSIGNED to POST
Actions #7

Updated by rchan over 1 year ago

  • Sprint changed from Sprint 99 to Sprint 100
Actions #8

Updated by rchan over 1 year ago

  • Sprint changed from Sprint 100 to Sprint 101
Actions #9

Updated by ipanova@redhat.com over 1 year ago

  • Sprint changed from Sprint 101 to Sprint 102
Actions #10

Updated by rchan over 1 year ago

  • Sprint changed from Sprint 102 to Sprint 103
Actions #11

Updated by rchan over 1 year ago

  • Sprint changed from Sprint 103 to Sprint 104
Actions #12

Updated by rchan over 1 year ago

  • Sprint changed from Sprint 104 to Sprint 105
Actions #13

Updated by rchan over 1 year ago

  • Sprint changed from Sprint 105 to Sprint 106
Actions #14

Updated by rchan over 1 year ago

  • Sprint changed from Sprint 106 to Sprint 107
Actions #15

Updated by rchan over 1 year ago

  • Sprint changed from Sprint 107 to Sprint 108
Actions #16

Updated by rchan over 1 year ago

  • Sprint changed from Sprint 108 to Sprint 109
Actions #17

Updated by rchan about 1 year ago

  • Sprint changed from Sprint 109 to Sprint 110
Actions #18

Updated by rchan about 1 year ago

  • Sprint changed from Sprint 110 to Sprint 111
Actions #19

Updated by rchan about 1 year ago

  • Sprint changed from Sprint 111 to Sprint 112
Actions #20

Updated by pulpbot about 1 year ago

  • Description updated (diff)
  • Status changed from POST to CLOSED - DUPLICATE

Also available in: Atom PDF