[ 
https://issues.apache.org/jira/browse/SOLR-13569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16869514#comment-16869514
 ] 

Jan Høydahl commented on SOLR-13569:
------------------------------------

Ok, first take on this is in [GitHub Pull Request 
#735|https://github.com/apache/lucene-solr/pull/735]

I found that there was some pre-existing HTML and CSS for environment already 
in the code base from the old UI, but not in use. So I fixed this a bit and put 
the colored bar on top of the menu instead of on top of the whole screen. 
Examples:

!prod-example.png|width=400!!test-example.png|width=400!

To set as cluster property, run e.g.
{code:java}
server/scripts/cloud-scripts/zkcli.sh -zkhost 127.0.0.1:9983 -cmd clusterprop 
-name environment -val "test"{code}
Added a RefGuide section to explain this.

> AdminUI visual indication of prod/test/dev environment
> ------------------------------------------------------
>
>                 Key: SOLR-13569
>                 URL: https://issues.apache.org/jira/browse/SOLR-13569
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Admin UI
>            Reporter: Jan Høydahl
>            Assignee: Jan Høydahl
>            Priority: Major
>         Attachments: Environment-hint.png, prod-example.png, test-example.png
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> To guard against accidentally changing the wrong cluster, we should add a 
> visual indication in the Admin UI of whether you currently work with a 
> production environment or not, e.g. a red bar on top with an optional 
> environment label, see sketch. The bar could by default be red for 
> production, yellow for test and green for dev.
>  !Environment-hint.png|width=700!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to