starlingx
/
openstack-armada-app
Code Issues Proposed changes

Fix custom horizon theme load 

When loading a custom theme, the current configuration also loads the
StarlingX theme which is not available on the Openstack Horizon image.
This fix removes the loading of the StarlingX theme and fixes the logic
so other themes are enabled when the custom one is not.

Closes-Bug: #1935859

Signed-off-by: Thiago Brito <thiago.brito@windriver.com>
Change-Id: I14975ee07210875f0e5c49c13e3371a18c4b2261
This commit is contained in:
Thiago Brito 2021-07-12 11:36:07 -03:00 committed by Thiago Paiva Brito
parent 1e4fb63116
commit ab3b60c197
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
stx-openstack-helm/stx-openstack-helm/manifests/manifest.yaml
View File

@ -3730,16 +3730,16 @@ data:
" parameters:[%(param)s] message:[%(message)s]"),
}
AVAILABLE_THEMES = [
('default', 'Default', 'themes/default'),
('material', 'Material', 'themes/material'),
]
# Custom Theme Override
for root, dirs, files in os.walk('/opt/branding/applied'):
if 'manifest.py' in files:
exec(open(os.path.join(root, 'manifest.py')).read())
AVAILABLE_THEMES = [
('default', 'Default', 'themes/default'),
('material', 'Material', 'themes/material'),
('starlingx', 'StarlingX', 'themes/starlingx'),
('custom', 'Custom', '/opt/branding/applied'),
]
AVAILABLE_THEMES.append(('custom', 'Custom', '/opt/branding/applied'))
DEFAULT_THEME = 'custom'
# Secure site configuration