Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/zilencer/management/commands/migrate_stream_notification...

18 lines
656 B
Python
Raw Normal View History

[manual] Add script to migrate subs to new stream notification settings. Previously, streams used `notifications`. Now they have separate `desktop_notifications` and `audible_notifications`. On staging, this should be run after the schema migration has been applied (and technically before the code that uses the new fields is deployed, but for staging, processing our notification settings a few minutes late won't hurt anyone). On prod, the script should be re-run just before the code using the new notification settings is deployed to process any customer notification settings changed since the staging deploy. (imported from commit d99d238cd1b317c5180d7f940d70a7e2f8f9c712)
2014-02-14 16:36:20 +01:00
Annotate most Zulip management commands.
2016-06-04 16:52:18 +02:00
from typing import Any
[manual] Add script to migrate subs to new stream notification settings. Previously, streams used `notifications`. Now they have separate `desktop_notifications` and `audible_notifications`. On staging, this should be run after the schema migration has been applied (and technically before the code that uses the new fields is deployed, but for staging, processing our notification settings a few minutes late won't hurt anyone). On prod, the script should be re-run just before the code using the new notification settings is deployed to process any customer notification settings changed since the staging deploy. (imported from commit d99d238cd1b317c5180d7f940d70a7e2f8f9c712)
2014-02-14 16:36:20 +01:00
from django.core.management.base import BaseCommand
python: Sort imports in smaller apps.
2017-11-16 00:55:49 +01:00
[manual] Add script to migrate subs to new stream notification settings. Previously, streams used `notifications`. Now they have separate `desktop_notifications` and `audible_notifications`. On staging, this should be run after the schema migration has been applied (and technically before the code that uses the new fields is deployed, but for staging, processing our notification settings a few minutes late won't hurt anyone). On prod, the script should be re-run just before the code using the new notification settings is deployed to process any customer notification settings changed since the staging deploy. (imported from commit d99d238cd1b317c5180d7f940d70a7e2f8f9c712)
2014-02-14 16:36:20 +01:00
from zerver.models import Subscription
class Command(BaseCommand):
help = """One-off script to migration users' stream notification settings."""
def handle(self, *args, **options):
Annotate most Zulip management commands.
2016-06-04 16:52:18 +02:00
# type: (*Any, **Any) -> None
[manual] Add script to migrate subs to new stream notification settings. Previously, streams used `notifications`. Now they have separate `desktop_notifications` and `audible_notifications`. On staging, this should be run after the schema migration has been applied (and technically before the code that uses the new fields is deployed, but for staging, processing our notification settings a few minutes late won't hurt anyone). On prod, the script should be re-run just before the code using the new notification settings is deployed to process any customer notification settings changed since the staging deploy. (imported from commit d99d238cd1b317c5180d7f940d70a7e2f8f9c712)
2014-02-14 16:36:20 +01:00
for subscription in Subscription.objects.all():
subscription.desktop_notifications = subscription.notifications
subscription.audible_notifications = subscription.notifications
subscription.save(update_fields=["desktop_notifications",
"audible_notifications"])