Another related question is, can we control the configuration categories that show up in UI? Based on scanning the code seems like its managed by ambari-web javascripts.
Thanks Sujeet On Wed, Sep 24, 2014 at 12:20 AM, Sujeet Varakhedi <[email protected]> wrote: > Sure. https://issues.apache.org/jira/browse/AMBARI-7466 > > Sujeet > > On Tue, Sep 23, 2014 at 11:12 AM, Yusaku Sako <[email protected]> > wrote: > >> Hi Sujeet, >> >> This is a bug. >> Ambari Web is not using these property-type attributes in the stack >> definition yet to determine whether it should be rendered as a >> password field or not. >> Can you go ahead and file a JIRA? >> >> Thanks, >> Yusaku >> >> On Tue, Sep 23, 2014 at 10:30 AM, Sujeet Varakhedi >> <[email protected]> wrote: >> > With a new service definition for HAWQ on PHD stack, I am creating a >> > configuration file with a password field for Admin Passwords. The field >> > shows up in UI but does not shadow user input. Known issue or I am >> missing >> > something. Here is how the config looks: >> > >> > <property require-input = "true"> >> > <name>hawq.user.password</name> >> > <value></value> >> > <property-type>PASSWORD</property-type> >> > <description>HAWQ Admin Password</description> >> > </property> >> > >> > >> > Sujeet >> >> -- >> CONFIDENTIALITY NOTICE >> NOTICE: This message is intended for the use of the individual or entity >> to >> which it is addressed and may contain information that is confidential, >> privileged and exempt from disclosure under applicable law. If the reader >> of this message is not the intended recipient, you are hereby notified >> that >> any printing, copying, dissemination, distribution, disclosure or >> forwarding of this communication is strictly prohibited. If you have >> received this communication in error, please contact the sender >> immediately >> and delete it from your system. Thank You. >> > >
