Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow Notifications for Non Multi-Tenant Scenarios #27

Closed
tsutomi opened this issue Apr 27, 2023 · 0 comments · Fixed by #29
Closed

Allow Notifications for Non Multi-Tenant Scenarios #27

tsutomi opened this issue Apr 27, 2023 · 0 comments · Fixed by #29
Assignees
Labels
enhancement New feature or request sender Issue related to the send capability

Comments

@tsutomi
Copy link
Member

tsutomi commented Apr 27, 2023

The notification service of the Deveel.Webhooks project is currently supporting only multi-tenant scenarios for the notifications, which requires additional configurations of the applications, to circumvent the limitation (eg. adding the multi-tenant support and use only one static tenant).

Although this is a feature that has sense in large-scale scenarios, in most of the situations this might be excessive and hard to handle.

The proposed solution might provide one or more of the two options:

  • Multi-Tenant Notifier - A notifier service that is requiring the identifier of the tenant to resolve webhook subscriptions, provided as alternative to another service that will not require this input and use the regular storage
  • Implicit Resolution of the Tenants - The notifier service will not require the unique identifier of the tenant to notify, scanning for all tenants registered in the current context, notifying to all subscriptions matching the event
  • Tenant Identifier in Event - The EventInfo structure might be extended with an optional the identifier of the tenant of the subscriptions to the event, to let the notifier identify and resolve subscriptions specific for that context
@tsutomi tsutomi added the enhancement New feature or request label Apr 27, 2023
@tsutomi tsutomi self-assigned this Apr 27, 2023
@tsutomi tsutomi linked a pull request Apr 27, 2023 that will close this issue
@tsutomi tsutomi added the sender Issue related to the send capability label Apr 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request sender Issue related to the send capability
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant