Currently the DMS installation script asks users for the DB passwords when they re-run a config (after a config has already been built and deployed).
However, this actually doesn't do anything, the PW are not changed, because DMS is not actually accessing the databases. The user has to login/access the DB themselves to change.
Investigate if DMS can support changing of PW, and if not, we may need to simply suppress/hide the PW questions when they re-run or update a config.
Currently the DMS installation script asks users for the DB passwords when they re-run a config (after a config has already been built and deployed).
However, this actually doesn't do anything, the PW are not changed, because DMS is not actually accessing the databases. The user has to login/access the DB themselves to change.
Investigate if DMS can support changing of PW, and if not, we may need to simply suppress/hide the PW questions when they re-run or update a config.