Description
As a developer of console, we often use a local bridge and running it as kube:admin. With the new ODC-4370 User settings feature it can be confusing if we all share one ConfigMap for our pinned resources, quick start process and so on.
As a developer I want to keep my user settings separate from other developers.
Acceptance Criteria
- Developers can (easily) use save their user settings in a separated area.
Implementation idea #1
- Provide a bridge parameter to prefix the user settings configmap with a string. BRIDGE_USER_SETTINGS_PREFIX ?
- Automatically set this parameter in oc-environment.sh script to the current environment variable $USER
- Use this parameter in api calls /api/console/usersettings to create prefixed ConfigMap, Role and RoleBinding
- Provide a new SERVER_FLAG "userSettingsPrefix"
- Extend the user settings hook to use the SERVER_FLAG to watch the correct ConfigMap as well.
Implementation idea #2 based on Christians and Sams feedback
- Provide a user settings cli parameter to use localStorage instead of ConfigMap
- Automatically set this parameter in oc-environment.sh script
- Provide a new SERVER_FLAG {{"userSettings" and e}}xtend the user settings hook to use this flag to use existing localStorage fallback
Additional Details:
None