When it comes about importing the third-party events, the framework provides a ThirdPartyContext tool.
However, in a multi-tenant application, the imported events were dispatched in a straightforward manner, without specifying the TenantId via TenantAwareRunner.
The corresponding test was also flawed: in fact, it was dispatching the events to a single-tenant Bounded Context.
This PR addresses the issue by fixing the test and making IntegrationBroker (an intermediary between ThirdPartyContext and "domestic" Bounded Contexts) to explicitly use TenantAwareOperation during the event dispatch.
armiol
commented
1 year ago
When it comes about importing the third-party events, the framework provides a
ThirdPartyContexttool.However, in a multi-tenant application, the imported events were dispatched in a straightforward manner, without specifying the
TenantIdviaTenantAwareRunner.The corresponding test was also flawed: in fact, it was dispatching the events to a single-tenant Bounded Context.
This PR addresses the issue by fixing the test and making
IntegrationBroker(an intermediary betweenThirdPartyContextand "domestic" Bounded Contexts) to explicitly useTenantAwareOperationduring the event dispatch.