-
Story
-
Resolution: Unresolved
-
Major
-
None
-
None
Long term, we want to migrate the admin perspective to its own dynamic plugin. In the short term, we can provide a flag to hide the perspective so that console can be used as a framework for building other experiences like HAC.
Acceptance Criteria
- The backend has a flag that will disable the admin perspective.
- When the flag is set, the admin perspective and its nav items are hidden.
- If there is only one perspective, hide the perspective switcher.
Non-goals
This story does not cover moving any of the admin console code out of the public package or migrating it to a dynamic plugin. That will be covered by separate stories in epic CONSOLE-2943.
[CONSOLE-2944] Allowing hiding the admin perspective through a server flag
Samuel Padgett
added a comment - Rotten issues close after 30d of inactivity.
You may reopen the issue by moving it back to TODO state and removing the `lifecycle-rotten` label. Exclude this issue from closing again by adding the `lifecycle-frozen` label.
Samuel Padgett
added a comment - Rotten issues close after 30d of inactivity.
You may reopen the issue by moving it back to TODO state and removing the `lifecycle-rotten` label. Exclude this issue from closing again by adding the `lifecycle-frozen` label. Samuel Padgett
added a comment - Stale issues rot after 30d of inactivity.
Mark the issue as fresh by removing the `lifecycle-rotten` label.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by adding the `lifecycle-frozen` label.
If this issue is safe to close now please do so.
Samuel Padgett
added a comment - Stale issues rot after 30d of inactivity.
Mark the issue as fresh by removing the `lifecycle-rotten` label.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by adding the `lifecycle-frozen` label.
If this issue is safe to close now please do so. Samuel Padgett
added a comment - Issues go stale after 90d of inactivity.
Mark the issue as fresh by removing the `lifecycle-stale` label.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by adding the `lifecycle-frozen` label.
If this issue is safe to close now please do so.
Samuel Padgett
added a comment - Issues go stale after 90d of inactivity.
Mark the issue as fresh by removing the `lifecycle-stale` label.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by adding the `lifecycle-frozen` label.
If this issue is safe to close now please do so. 
Rotten issues close after 30d of inactivity.
You may reopen the issue by moving it back to TODO state and removing the `lifecycle-rotten` label. Exclude this issue from closing again by adding the `lifecycle-frozen` label.