While fixing issue 14981 to not have create-domain prompt for the
master password unless --usemasterpassword is specified, it occurred to
me that create-local-instance must be doing something with this since it
has a --savemasterpassword option too. As it turns out,
create-local-instance already has logic such that it only prompts for
the master password if --savemasterpassword is specified. So this is
actually broken if a user wants to have a non-default master password
but not save it to disk.
I was going to fix this as part of 14981, but since Jennifer is making
changes to create-local-instance in this area, and the location of the
master-password file is being moved to the node, etc., maybe it would be
better to fix this as part of the issue that move the master password
file on the instances. (14989).
Also, issue 14990 requests changes to change-master-password to support
changing it for a node. Jennifer, do you want to fix 14990 to since
that work needs to be coordinated with 14989?
Thanks.
Tom