Added always_confirm_no option

[dsmurrell]

I could have missed something, but I didn't see an option to, without manual intervention, confirm 'no' to some required migration.

We have a situation where evolve is run remotely and we wanted to automatically confirm 'no' if a migration was required to allow the program to not wait forever. Setting interactive=False would always enact the migration.

Is there another way of doing this currently?

The only thing that doesn't quite gel with this addition is that to get the bright red output:

Making updates to database: dbname

interactive needs to be True with a call like db.evolve(interactive=True, always_confirm_no=True)

and this seems weird if you're using this option for automated operation. Was there a reason you only output "Making updates to database: dbname" if interactive is True?

[dsmurrell]

Sorry, I couldn't seem to run the tests locally as I kept getting peewee.OperationalError: (1045, "Access denied for user 'user'@'localhost' (using password: NO)")

[keredson]

so this would be as a no-op check during deployment, right?

if so, yeah, makes sense. but not crazy about always_confirm_no. maybe confirm_noop? fail_if_not_current? let's brainstorm names, open to other suggestions.

[keredson]

re local testing, where did it fail w/ that? at createdb peeweedbevolve_test? can you open a bug w/ the stacktrace? at min i should doc steps or catch and give better error.

[dsmurrell]

It does this for a while (about 5 times the amount in that screenshot)...

and then it does this without stopping...

and when I ctrl-c out it does this...

Let me know if there is a way I can provide more info. It seems that I'm not giving the right password etc to my local postgres instance, but I'm not sure how to do that in the tests.