Aligns the code base with this decision-record, specifically the delete-participant action.
In doing so, the following changes were made
new event type ParticipantContextDeleting was introduced to signal an impending deletion. This event is consumed by the ParticipantContextEventCoordinator that triggers the DidDocumentService to unpublish and delete the DID Docs, and the KeyPairService to revoke the key.
the DidDocumentService does not consume the ParticipantContextDeleted event anymore, because it gets invoked directly by the coordinator
KeyPairServiceImpl: added transaction context
unpublishing DIDs: the check if a DidDocument is in PUBLISHED state was moved from the publisher to the DidDocumentService
Why it does that
alignment with the decision decision-records
Further notes
other changes in the PR may not yet correctly reflect other sections of the D-R, those will get refactored in subsequent PRs.
What this PR changes/adds
Aligns the code base with this decision-record, specifically the delete-participant action.
In doing so, the following changes were made
new event type
ParticipantContextDeletingwas introduced to signal an impending deletion. This event is consumed by theParticipantContextEventCoordinatorthat triggers theDidDocumentServiceto unpublish and delete the DID Docs, and theKeyPairServiceto revoke the key.the
DidDocumentServicedoes not consume theParticipantContextDeletedevent anymore, because it gets invoked directly by the coordinatorKeyPairServiceImpl: added transaction contextunpublishing DIDs: the check if a DidDocument is in
PUBLISHEDstate was moved from the publisher to theDidDocumentServiceWhy it does that
alignment with the decision decision-records
Further notes
other changes in the PR may not yet correctly reflect other sections of the D-R, those will get refactored in subsequent PRs.
Linked Issue(s)
Closes # <-- insert Issue number if one exists
_Please be sure to take a look at the contributing guidelines and our etiquette for pull requests._