From c39397d028c2c729ad6728dec31c427451ff9fc6 Mon Sep 17 00:00:00 2001 From: Tim Flink Date: Mon, 11 Mar 2019 18:57:36 +0000 Subject: [PATCH] blockerbugs: changing SQLALCHEMY option in stg to reduce cron email There was a change with a recent upgrade to flask-sqlalchemy so that SQLALCHEMY_TRACK_MODIFICATIONS will no longer be enabled by default in future releases. As we're not using it, I'm explicitly setting that to False in the hopes that most/some of the cron emails go away if the warning isn't emitted during blockerbugs sync. --- roles/blockerbugs/templates/blockerbugs-settings.py.j2 | 1 + 1 file changed, 1 insertion(+) diff --git a/roles/blockerbugs/templates/blockerbugs-settings.py.j2 b/roles/blockerbugs/templates/blockerbugs-settings.py.j2 index 03876c1142..bcb54e5af0 100644 --- a/roles/blockerbugs/templates/blockerbugs-settings.py.j2 +++ b/roles/blockerbugs/templates/blockerbugs-settings.py.j2 @@ -7,6 +7,7 @@ FAS_PASSWORD = "{{ blockerbugs_fas_password }}" FAS_FLASK_COOKIE_REQUIRES_HTTPS = False FAS_CHECK_CERT = False PRODUCTION = False +SQLALCHEMY_TRACK_MODIFICATIONS = False {% endif %} BUGZILLA_URL = '{{ blockerbugs_bugzilla_url }}' BODHI_URL = '{{ blockerbugs_bodhi_url }}'