Project

General

Profile

Actions

Refactor #12747

closed

Provide some kind of central store or consistent way to manage dynamically registered objects from plugins

Added by Stephen Benjamin over 8 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Plugin integration
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Currently, there are number of things you can register for plugins - compute resources, dashboard widgets, etc.

Dashboard widgets stores plugin registered widgets like this: https://github.com/theforeman/foreman/blob/develop/app/services/dashboard/manager.rb#L3
Compute resource store plugin registered resources like this: https://github.com/theforeman/foreman/blob/develop/app/models/compute_resource.rb#L13

It's all very inconsistent. We should standardize on a single way, perhaps even having some kind of central store to put this kind of data.

The problem when we re-invent this for every new dynamically registered thing, we introduce potential problems, like #12746.


Related issues 4 (0 open4 closed)

Related to Foreman - Bug #12746: Compute resources can disappear in a development instanceClosedDominic Cleal12/08/2015Actions
Related to Foreman - Bug #14300: after removing dashboard widgets none are listed to add backDuplicate03/21/2016Actions
Related to Foreman - Bug #14742: Template kind friendly names from plugins can be reloaded and lost in developmentClosedDominic Cleal04/21/2016Actions
Related to Foreman - Bug #14969: Custom status is not reloaded correctlyClosedMarek Hulán05/09/2016Actions
Actions

Also available in: Atom PDF