populate_db: Don't enqueue push notifications service updates.

Since we're just creating an initial database state, there's no reason
we need to submit increment analytics updates to the bouncer service;
such updates will happen during queue worker startup, if needed.
This commit is contained in:
Tim Abbott 2024-04-18 09:17:04 -07:00
parent 72018cc26b
commit 951a474376
1 changed files with 3 additions and 0 deletions

View File

@ -75,6 +75,9 @@ from zerver.models.users import get_user, get_user_by_delivery_email, get_user_p
from zilencer.models import RemoteRealm, RemoteZulipServer, RemoteZulipServerAuditLog from zilencer.models import RemoteRealm, RemoteZulipServer, RemoteZulipServerAuditLog
from zilencer.views import update_remote_realm_data_for_server from zilencer.views import update_remote_realm_data_for_server
# Disable the push notifications bouncer to avoid enqueuing updates in
# maybe_enqueue_audit_log_upload during early setup.
settings.PUSH_NOTIFICATION_BOUNCER_URL = None
settings.USING_TORNADO = False settings.USING_TORNADO = False
# Disable using memcached caches to avoid 'unsupported pickle # Disable using memcached caches to avoid 'unsupported pickle
# protocol' errors if `populate_db` is run with a different Python # protocol' errors if `populate_db` is run with a different Python