Project

Profile

Help

Story #4944

As a user, I can uninstall plugin and remove all the relevant data

Added by ttereshc 4 months ago. Updated 4 months ago.

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

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

Currently there is no way to uninstall a plugin together with removing data related to it.

If there is a need for that or not is still a question.
At the very least, let's document how to do it manually (if possible) or just state the fact that it's not supported.

Use cases to cover:
- install a plugin, do nothing (no sync, upload, etc), uninstall the plugin
- install a plugin, use it, uninstall the plugin

History

#1 Updated by ttereshc 4 months ago

  • Description updated (diff)

#2 Updated by mdepaulo@redhat.com 4 months ago

As a sysadmin at my last job, we only used Pulp as part of Satellite.
(We were phasing out rsync scripts from other parts of our environment.)

If we had used Pulp directly:
1. The inability to uninstall plugins would not be a big deal. Assuming they don't slow down Pulp (despite having no content), complicate the UI, etc.
2. If we did uninstall it, we would definitely want to cleanup the disk space / content (either at plugin uninstall time, or after).
3. If we did uninstall it, we would have only a small preference for it to cleanup the database. But it wouldn't be a big deal. We would never poke around in the database to see if it was removed. And we would only really care if we suspected that Pulp was not working because of the plugin having been previously installed. We would definitely care if we reinstalled it (much) later, and it didn't work. Compare this to how on Windows, when you uninstall an app, it usually has lots of leftover state in the registry. Leftover "cruft" is a fact of life, especially on Windows. And you eliminate cruft by rebuilding the server, including the application state.

Also, the inability to uninstall the file plugin specifically would be OK with us, assuming the above from #1. We would probably use for testing purposes if we suspected the other plugin we needed was not working. We would treat it like a reference plugin.

Please register to edit this issue

Also available in: Atom PDF