Hi Jungtaek, Basically, I agree with you to show environments of Zeppelin. I think we just hide those information which is like a password only, or have an option whether we show or not with - for instance - ZEPPELIN_SHOW_ENVIRONMENT.
How about you? Regards, Jongyoul On Wed, Jan 6, 2016 at 3:04 PM, Jungtaek Lim <[email protected]> wrote: > Hi devs, > > I followed up pull request for ZEPPELIN-543 > <https://github.com/apache/incubator-zeppelin/pull/582> and think it may > be > better to have page to Zeppelin Web UI and let page shows variables for > Zeppelin, and loaded repositories, and so on. > > I think we can start with showing variables for Zeppelin. > I can find variables from Confvars, but someone may don't like to expose > some key / value pairs to the Web UI since it contains > ZEPPELIN_SSL_KEY_MANAGER_PASSWORD, ZEPPELIN_SSL_KEYSTORE_PASSWORD, > ZEPPELIN_SSL_TRUSTSTORE_PASSWORD. > Someone could complain that why ZEPPELIN_HOME is exposed to Web UI. > > So what key / value pairs should be excluded? When consensus will be made > I'll follow up the next work. > > Thanks! > Jungtaek Lim (HeartSaVioR) > > -- > Name : Jungtaek Lim > Blog : http://medium.com/@heartsavior > Twitter : http://twitter.com/heartsavior > LinkedIn : http://www.linkedin.com/in/heartsavior > -- 이종열, Jongyoul Lee, 李宗烈 http://madeng.net
