Project

General

Profile

Feature #3588

Uninstall plugins - from GUI or command line

Added by Benjamin Papillon over 5 years ago. Updated over 5 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Plugins-Engines
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

Actually, there is no documentation nor feature on gui to uninstall plugins.

A Ticket is already open for listing plugins. Being able to uninstall and/or disable them would be handy to troubleshoot weird issues. (Ex. #3570)


Related issues

Related to Foreman - Feature #3510: As a GUI user, I would like to know what plugins are installedClosed2013-10-25
Related to Salt - Feature #10859: Instructions on how to remove the Salt Plugin and upgrading between major foreman versionsNew2015-06-17
Related to Foreman - Bug #10850: Uninstalling a plugin with a dashboard leads to "Template is missing" error in the uiClosed2015-06-17
Related to Foreman - Bug #12645: Reports throw error with unknown mailers when plugin is uninstalledNew2015-12-01
Related to Installer - Bug #16747: Foreman-Installer puppetdb plugin cleanupNew2016-09-29
Related to Foreman - Tracker #19454: Mark plugin migrations to be able to run them separately for each plugin.Assigned2017-05-03

Related to Foreman - Bug #8272: Plugins don't cleanup after themselves during uninstallationNew2014-11-04
Related to Templates - Feature #19260: Add clean up jobClosed2017-04-12

History

#1 Updated by Benjamin Papillon over 5 years ago

  • Related to Feature #3510: As a GUI user, I would like to know what plugins are installed added

#2 Updated by Benjamin Papillon over 5 years ago

  • Description updated (diff)

#3 Updated by Dominic Cleal over 5 years ago

  • Category changed from Web Interface to Plugins-Engines

We have talked about a Jenkins-style plugin manager where we might be able to add/remove plugins on the fly. Currently we're relying on the system package manager for RPMs and bundler otherwise, so it's a bit trickier.

This does hint at another looming issue, which is that some plugins should have an uninstallation/purge procedure which removes certain data from Foreman's database. As plugins get more advanced, it's likely that they leave things like STI data in tables or foreign keys that might interfere with running of the standalone Foreman app.

#4 Updated by Benjamin Papillon over 5 years ago

This is calling for another ticket :D

Add guidelines to help plugin writers so that they plan and document an uninstall feature.

Shall I create it? ;-)

#5 Updated by Dominic Cleal over 5 years ago

Sure, thanks! :)

#6 Updated by Stephen Benjamin over 3 years ago

  • Related to Feature #10859: Instructions on how to remove the Salt Plugin and upgrading between major foreman versions added

#7 Updated by Dominic Cleal over 3 years ago

  • Related to Bug #10850: Uninstalling a plugin with a dashboard leads to "Template is missing" error in the ui added

#8 Updated by Dominic Cleal over 3 years ago

  • Related to Bug #12645: Reports throw error with unknown mailers when plugin is uninstalled added

#9 Updated by Dominic Cleal over 2 years ago

  • Related to Bug #16747: Foreman-Installer puppetdb plugin cleanup added

#10 Updated by Shimon Shtein almost 2 years ago

  • Related to Tracker #19454: Mark plugin migrations to be able to run them separately for each plugin. added

#11 Updated by Marek Hulán almost 2 years ago

  • Related to Bug #8272: Plugins don't cleanup after themselves during uninstallation added

#12 Updated by Marek Hulán almost 2 years ago

Also available in: Atom PDF