Skip to content

Commit 8ee484e

Browse files
committed
🔥 [open-zaak/open-zaak#1203] Remove old envvars
remove old notification retry envvars, and update the docs accordingly
1 parent 22bd59a commit 8ee484e

3 files changed

Lines changed: 1 addition & 26 deletions

File tree

docs/delivery_guarantees.rst

Lines changed: 1 addition & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -69,15 +69,7 @@ On delivery failure, Open Notificaties will automatically retry delivery, with
6969
exponential backoff. E.g. the first retry will be done after one second, the next after
7070
two seconds and the third after 4 seconds.
7171

72-
The parameters for this can be :ref:`configured <installation_config_index>`:
73-
74-
* ``NOTIFICATION_DELIVERY_MAX_RETRIES``: the maximum number of automatic retries. After
75-
this amount of retries, Open Notificaties stops trying to deliver the message.
76-
* ``NOTIFICATION_DELIVERY_RETRY_BACKOFF``: if specified, a factor applied to the
77-
exponential backoff. This allows you to tune how quickly automatic retries are
78-
performed.
79-
* ``NOTIFICATION_DELIVERY_RETRY_BACKOFF_MAX``: an upper limit to the exponential
80-
backoff time.
72+
The parameters for this are described and can be configured in the admin interface, under ``Configuration > Notification component configuration``.
8173

8274
On top of that, via the admin interface you can manually select notifications to retry
8375
delivery for.

docs/installation/configuration/env_config.md

Lines changed: 0 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -98,16 +98,6 @@ on Docker, since `localhost` is contained within the container:
9898

9999
* `CELERY_RESULT_BACKEND`: the backend where the results of tasks will be stored (default: `redis://localhost:6379/1`)
100100

101-
* `NOTIFICATION_DELIVERY_MAX_RETRIES`: the maximum number of retries Celery will do if sending a notification failed.
102-
103-
* `NOTIFICATION_DELIVERY_RETRY_BACKOFF`: a boolean or a number. If this option is set to
104-
`True`, autoretries will be delayed following the rules of exponential backoff. If
105-
this option is set to a number, it is used as a delay factor.
106-
107-
* `NOTIFICATION_DELIVERY_RETRY_BACKOFF_MAX`: an integer, specifying number of seconds.
108-
If ``retry_backoff`` is enabled, this option will set a maximum delay in seconds
109-
between task autoretries. By default, this option is set to 48 seconds.
110-
111101
### Cross-Origin-Resource-Sharing
112102

113103
The following parameters control the CORS policy.

src/nrc/conf/includes/base.py

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -469,13 +469,6 @@
469469
CELERY_BROKER_URL = config("CELERY_BROKER_URL", "amqp://127.0.0.1:5672//")
470470
CELERY_RESULT_BACKEND = config("CELERY_RESULT_BACKEND", "redis://localhost:6379/1")
471471

472-
# Retry settings for delivering notifications to subscriptions
473-
NOTIFICATION_DELIVERY_MAX_RETRIES = config("NOTIFICATION_DELIVERY_MAX_RETRIES", 5)
474-
NOTIFICATION_DELIVERY_RETRY_BACKOFF = config("NOTIFICATION_DELIVERY_RETRY_BACKOFF", 3)
475-
NOTIFICATION_DELIVERY_RETRY_BACKOFF_MAX = config(
476-
"NOTIFICATION_DELIVERY_RETRY_BACKOFF_MAX", 48
477-
)
478-
479472
#
480473
# DJANGO-ADMIN-INDEX
481474
#

0 commit comments

Comments
 (0)