8303782f1e
The root cause of 1479018 was the mixed method for loading content in horizon. This patch moves horizon to load purely from enabled files. There are a couple of things that were required to allow this change. 1) Adding a mechanism, can_register() to horizon/base.py to handle the configuration based loading checks that had been accumulating in the panel.py files. This is an optional static method in Panel to encapsulate such configuration (read settings) based panel loading logic. And added testing for and documentation for this addition. 2) Create a numbering scheme for plugins. Moved the base dashboards to _1000_project.py _2000_admin.py _3000_identity.py _5000_settings.py. then populated the required panel_group and panel enabled files sparsely in those ranges. The sparseness is to allow for future additions. Additionally, I moved the already added Angular based panels next to their Django counterparts. Once the configuration loading was normalized, the bug reported in 1479018 was resolved and tests work with plugins panels in all dashboards. Close-Bug: #1479018 Partially implements: blueprint plugin-sanity Change-Id: I657e7ce37b2593a901a859cebf3d6ff8ada91941
9 lines
340 B
Python
9 lines
340 B
Python
from django.utils.translation import ugettext_lazy as _
|
|
|
|
# The slug of the panel group to be added to HORIZON_CONFIG. Required.
|
|
PANEL_GROUP = 'database'
|
|
# The display name of the PANEL_GROUP. Required.
|
|
PANEL_GROUP_NAME = _('Database')
|
|
# The slug of the dashboard the PANEL_GROUP associated with. Required.
|
|
PANEL_GROUP_DASHBOARD = 'project'
|