Leo Hemsted b01ec05aaf run migrations if app is down ...

normally we check the app's status page to see if migrations need
running. However, if the _status endpoint doesn't respond with 200, we
don't necessarily want to abort the deploy - we may be trying to deploy
a code fix that fixes that status endpoint for example.

We don't know whether to run the migrations or not, so err on the side
of caution by re-running the migration. The migration itself might be
the fix that gets the app working after all.

had to do a little song and dance because sometimes the response won't
be populated before an exception is thrown

2020-06-26 15:28:28 +01:00

..

bootstrap.sh

Revert "Celery 4"

2018-10-09 13:27:49 +01:00

check_if_new_migration.py

run migrations if app is down

2020-06-26 15:28:28 +01:00

common_functions.sh

…

delete_sqs_queues.py

use flake8 instead of pycodestyle

2017-11-28 14:28:01 +00:00

fix_migrations.py

add warning to fix_migrations script for when the filename is different

2017-12-07 10:41:10 +00:00

paas_app_wrapper.sh

Reduce concurrency and prefetch count of reporting celery app

2020-04-28 10:47:46 +01:00

run_app_paas.sh

Change how the bash script is started.

2019-10-31 16:41:16 +00:00

run_app.sh

Remove flask-script, move commands to click

2017-11-23 17:04:58 +00:00

run_celery_beat.sh

…

run_celery.sh

Add a stop celery script into the scripts folder.

2017-02-08 16:17:50 +00:00

run_multi_worker_app_paas.sh

Catch the TERM signal in the run_app_*paas scripts

2019-10-29 17:21:16 +00:00

run_single_test.sh

…

run_tests.sh

remove unused pytest flags

2020-02-13 12:52:12 +00:00