Bug 1908687 - Option to save user settings separate when using local bridge (affects console developers only)
Summary: Option to save user settings separate when using local bridge (affects consol...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.7.0
Assignee: Christoph Jerolimov
QA Contact: Gajanan More
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-17 10:57 UTC by Christoph Jerolimov
Modified: 2021-02-24 15:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 15:46:22 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 7586 0 None closed Bug 1908687: Use localstorage fallback when running a local bridge 2021-01-25 11:22:09 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:46:37 UTC

Description Christoph Jerolimov 2020-12-17 10:57:51 UTC 
Description of problem:
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.
Comment 2 Debsmita Santra 2021-01-25 11:27:49 UTC 
This is a feature for developers who starts a local bridge. So marking this as done
Comment 5 errata-xmlrpc 2021-02-24 15:46:22 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:5633
Note You need to log in before you can comment on or make changes to this bug.