69c799734b
The subscription confirmation feature will contain four patches: 1. webhook with mongoDB 2. email with mongoDB 3. webhook with redis 4. email with redis This patch is the first part of subscription confirmation feature for webhook with MongoDB. Others will be achieved in follow patches. This patch did: 1. Add v2/queue/<queue_name>/subscription/<subscription_id>/confirm endpoint. 2. Add a new config option: "require_confirmation". 3. Add a new property "confirmed" to subscription resource for MongoDB driver. 4. Add a new policy "subscription: confirm". 5. Add a new property "message type" for notification. 6. Use the pre-signed url in confirm request. 8. Re-use POST subscription to allow re-confirm. 9. Update notification for webhook subscription with mongoDB. 10. Support unsubscrib the subscription 11. Add tests for the feature. 12. Add doc and sample. Docimpact APIimpact Change-Id: Id38d4a5b4f9303b12e22e2b5c248facda4c00143 Implements: blueprint subscription-confirmation-support
10 lines
484 B
YAML
10 lines
484 B
YAML
---
|
|
features:
|
|
- Now before users send messages to subscribers through a queue, the
|
|
subscribers should be confirmed first. Zaqar only sends messages to the
|
|
confirmed subscribers. This feature supports "webhook" and "mailto"
|
|
subscribers with mongoDB or redis backend. The "mailto" part will be done
|
|
in O cycle. Set "require_confirmation = True" to enable this feature. The
|
|
default value is "False" now and we will enable it by default after one or
|
|
two cycles.
|