add installer breakpoint

[donsizemore]

Closes #349

[pdurbin]

This seems to work well! I just ran this:

ec2/ec2-create-instance.sh -g tests/group_vars/jenkins.yml -a 349_installer_kill_switch

And the playbook exited early with this:

TASK [dataverse : installer breakpoint] ****************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "You may now run the installer as dataverse in /tmp/dvinstall with python ./install.py -f --config_file=default.config"}

[pdurbin]

Oh, one thing is that the output stops with the message without printing the "how to terminate message". It looks like this:

TASK [dataverse : installer breakpoint] ****************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "You may now run the installer as dataverse in /tmp/dvinstall with python ./install.py -f --config_file=default.config"}

NO MORE HOSTS LEFT *************************************************************

PLAY RECAP *********************************************************************
localhost                  : ok=238  changed=126  unreachable=0    failed=1    skipped=139  rescued=0    ignored=0 

So I have to scroll up to find this message (which is printed early):

When you are done, please terminate your instance with:
aws  ec2 terminate-instances --instance-ids i-061929d8d8a9ff35a

[pdurbin]

I get this error: Couldn't create database or database already exists.

I'm working around it by dropping the database.

How hard would it be to not create the database when the installer breakpoint is set to true?

[donsizemore]

I get this error: Couldn't create database or database already exists.

I'm working around it by dropping the database.

How hard would it be to not create the database when the installer breakpoint is set to true?

You would always want a database and user created. Dataverse-Ansible simply launches the installer with -f