You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever we are publishing a webhook event to a particular tenant, we should also be able to send the same webhook event to the operator tenant. The operator tenant can use it just for informational purposes, or potentially can do actions on-behalf of tenants.
For example, an operator can be the one that manages asset liquidity on-behalf of tenants. This would require them to receive liquidity low webhook events.
Ideally in the future, the operator can subscribe to certain webhook events only, but for now, if a setting is enabled, we can duplicate publish all of the webhooks to the operator tenant.
Keep in mind not to double publish a webhook event that is already destined for the operator tenant.
Todos
If a webhook event is being published to a non-operator tenant, also publish the event also to the operator tenant (if a env variable is enabled)
The text was updated successfully, but these errors were encountered:
Context
Whenever we are publishing a webhook event to a particular tenant, we should also be able to send the same webhook event to the operator tenant. The operator tenant can use it just for informational purposes, or potentially can do actions on-behalf of tenants.
For example, an operator can be the one that manages asset liquidity on-behalf of tenants. This would require them to receive liquidity low webhook events.
Ideally in the future, the operator can subscribe to certain webhook events only, but for now, if a setting is enabled, we can duplicate publish all of the webhooks to the operator tenant.
Keep in mind not to double publish a webhook event that is already destined for the operator tenant.
Todos
The text was updated successfully, but these errors were encountered: