feat: implements EDR cache receiver + E2E tests #4004
Merged
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.
What this PR changes/adds
implements EDR cache receiver + E2E tests specifically:
edr-store-receiver
extension that will automatically cache theDataAddress
when the transfer process starts on the consumer side. It uses the event mechanism to also keep the cache sync with the transfer status (completed/terminated). With a settingedc.edr.receiver.sync
it can be configured to operate in a synchronous way (async by default).TransferProcessEvent
base class for transfer process events has been refactor to host all the common fields for transfer process events likeassetId
,type
andcontractId
EndToEndTransferParticipant
for E2E test by extracting it to a base class which can be extended for custom/additional use caseEDR
API instead of using remote callbacks for getting access to the EDR associated to the transfer process. This also covers the case of contract expiry, ensuring that the EDR is purged on transfer termination by thePolicyMonitor
Why it does that
data plane signaling
Further notes
List other areas of code that have changed but are not necessarily linked to the main feature. This could be method
signature changes, package declarations, bugs that were encountered and were fixed inline, etc.
Linked Issue(s)
Closes #3998
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.