Project

General

Profile

Actions

Feature #3588

open

Uninstall plugins - from GUI or command line

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

Status:
New
Priority:
Normal
Assignee:
-
Category:
Plugin integration
Target version:
-
Difficulty:
Triaged:
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 8 (4 open4 closed)

Related to Foreman - Feature #3510: As a GUI user, I would like to know what plugins are installedClosedAmos Benari10/25/2013Actions
Related to Salt - Feature #10859: Instructions on how to remove the Salt Plugin and upgrading between major foreman versionsNew06/17/2015Actions
Related to Foreman - Bug #10850: Uninstalling a plugin with a dashboard leads to "Template is missing" error in the uiClosedIvan Necas06/17/2015Actions
Related to Foreman - Bug #12645: Reports throw error with unknown mailers when plugin is uninstalledResolvedActions
Related to Installer - Bug #16747: Foreman-Installer puppetdb plugin cleanupNew09/29/2016Actions
Related to Foreman - Tracker #19454: Mark plugin migrations to be able to run them separately for each plugin.AssignedShimon Shtein05/03/2017

Actions
Related to Foreman - Bug #8272: Plugins don't cleanup after themselves during uninstallationNewActions
Related to Templates - Feature #19260: Add clean up jobClosedMarek Hulán04/12/2017Actions
Actions #1

Updated by Benjamin Papillon over 10 years ago

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

Updated by Benjamin Papillon over 10 years ago

  • Description updated (diff)
Actions #3

Updated by Dominic Cleal over 10 years ago

  • Category changed from Web Interface to Plugin integration

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.

Actions #4

Updated by Benjamin Papillon over 10 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? ;-)

Actions #5

Updated by Dominic Cleal over 10 years ago

Sure, thanks! :)

Actions #6

Updated by Stephen Benjamin about 9 years ago

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

Updated by Dominic Cleal over 8 years ago

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

Updated by Dominic Cleal over 8 years ago

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

Updated by Dominic Cleal almost 8 years ago

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

Updated by Shimon Shtein about 7 years ago

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

Updated by Marek Hulán about 7 years ago

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

Updated by Marek Hulán about 7 years ago

Actions

Also available in: Atom PDF