Prior to v2 I was able to run caprover deploy -d in the knowledge that if the CapRover machine password is no longer valid then I would be prompted for the current password and then the process would continue. Now, it just seems to bail out without a prompt:
Something bad happened: cannot deploy myapp at myserver.
Password is incorrect.
I prefer the previous behaviour... seems more user friendly just to be able to enter the password rather than having to go through the deploy process again without relying on defaults.
Prior to v2 I was able to run
caprover deploy -din the knowledge that if the CapRover machine password is no longer valid then I would be prompted for the current password and then the process would continue. Now, it just seems to bail out without a prompt:I prefer the previous behaviour... seems more user friendly just to be able to enter the password rather than having to go through the deploy process again without relying on defaults.