Closed abujeda closed 2 years ago
We have started working on this feature. Draft PR coming shortly
One thing on implantation that I'd expect is moving all these env variables to string_configs
if they're simple. I.e, default or value. some have more complicated toggling logic. If that's the case, they can have their own function, but I'd say most can move here.
I was actually updating the implementation of the UserConfiguration
based on the string_configs
feature from ConfigurationSingleton
. More details with the PR soon.
I see, you just duplicate the same blocks. That could work too.
Just to be on the same page. These are the changes: https://github.com/OSC/ondemand/pull/2151
Still work in progress and not completed, but the general idea is there. Let me know what you think.
Small demo of what is possible with the OnDemand Branding setup using the new profile based configuration:
This was fixed in #2151.
At IQSS, we have a requirement to support different look and feel for different departments. Moving the existing branding customizations to new profile feature will allow us to implement some of these requirements.
Definition of Done Move the following environment values from
ConfigurationSingleton
toUserConfiguration
OOD_DASHBOARD_TITLE
OOD_DASHBOARD_LOGO
OOD_DASHBOARD_LOGO_HEIGHT
OOD_PUBLIC_URL
OOD_BRAND_BG_COLOR
OOD_BRAND_LINK_ACTIVE_BG_COLOR
OOD_DASHBOARD_HEADER_IMG_LOGO
OOD_NAVBAR_TYPE
Update the UserConfiguration functionality to read from the
ENV
object first before using theconfig
object data. Values in theENV
object will have precedence over values in theconfig
object.Update all references to these values from the ConfigurationSingleton to the new UserConfiguration object.
┆Issue is synchronized with this Asana task by Unito