cdh-web QA deploy playbook

[thatbudakguy]

I'm currently able to run the playbook successfully start to finish, but http://cdh-test-web1.princeton.edu/ times out (I am on VPN). You need to have the community.general ansible collection installed to run it; see the README for the command to do that. You can run the playbook with: ansible-playbook playbooks/cdh-web_qa.yml.

Tons of changes, since this involved touching virtually every role in some way, although for many of them it was just adding privilege escalation (and maybe a default or two). I also haven't messed with the tests for the postgresql role yet. Hoping more eyes on it will help clean up this massive PR.

[rlskoeser]

@thatbudakguy cdh-test-web1 is the server name, not the url — the ones we'd planned to use are documented here:
pulibrary/princeton_ansible#1798

— That reminds me, we'll need to update the allowed hostnames config.

[rlskoeser]

Some comments and questions, but generally I think this looks good. Was able to pull the latest version of the branch and run the molecule tests successfully.

You tested the new deploy, but might be good to test an old qa deploy also to make sure they still work.

[rlskoeser]

Updates since last time all look good to me.

[kayiwa]

Love your deploy user tests!
postgresql looks good also.

[thatbudakguy]

@rlskoeser two things still need a decision before merging, I think:

• should we try to add tests for the postgres role? there still aren't any that use the PUL approach of running postgres locally to test against.
• should we try your suggestion of not making database backups if the database has only just been created? seems like low to medium effort, but we would also probably want to test it.

[rlskoeser]

@thatbudakguy thanks for identifying what's left and where you need me to weigh in.

At this point, I don't want to hold up the migration work any further.

@rlskoeser two things still need a decision before merging, I think:

• should we try to add tests for the postgres role? there still aren't any that use the PUL approach of running postgres locally to test against.

I'd like to put this off. Would you make an issue to add a test? Can we set up a time down the road to pair with Francis on that, or borrow from the example hello world postrges role work he was doing for us?

• should we try your suggestion of not making database backups if the database has only just been created? seems like low to medium effort, but we would also probably want to test it.

I don't think it's worth holding up the deploy, since it's pretty minor and not a huge downside (not a heavy cost for backing up an empty database). Should we make an issue to document it? I don't think it's a huge priority, but might be easy to fold in and test once we have the postgres role tested.

[thatbudakguy]

created #52 and #53 to track the above. for the postgres tests (#52), i think we know how to do it, so we can implement it and then tag francis for review.