[1.x] Import events from 3rd-party with respect for tenancy #1503
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
viaTenantAwareRunner
.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 betweenThirdPartyContext
and "domestic" Bounded Contexts) to explicitly useTenantAwareOperation
during the event dispatch.