Skip to content

Commit DID operations and publication queues atomically - #1316

Merged
Bushstar merged 2 commits into
mainfrom
bush/atomic-operation-publication
Sep 29, 2026
Merged

Bushstar merged 2 commits into
mainfrom
bush/atomic-operation-publication

Conversation

@Bushstar

Copy link
Copy Markdown
Contributor

Overview

Gatekeeper previously persisted accepted create and update operations before adding them to mediator publication queues. A queue failure could therefore leave a DID changed locally while the API reported failure and the operation was never published.

This change commits the event, index change, and required publication queue entries within one database operation.

Changes

  • Add a required atomic event-and-queue method to the Gatekeeper database adapter contract
  • Implement the atomic boundary for JSON, SQLite, Redis, PostgreSQL, and MongoDB
  • Preserve normal non-publishing event imports through the existing event method
  • Consolidate duplicate legacy Mongo queue documents before enforcing one queue per registry
  • Add regression coverage for queue failures, retries, adapter behavior, and Mongo upgrades

Store accepted events and publication queue entries in one adapter transaction so queue failures cannot strand local-only operations.\n\nConsolidate duplicate Mongo queue documents before enforcing unique registry queues.
@Bushstar
Bushstar requested a review from jahatch512 September 29, 2026 06:24
jahatch512
jahatch512 previously approved these changes Sep 29, 2026
…-publication

# Conflicts:
#	tests/gatekeeper/crud.test.ts
@Bushstar
Bushstar merged commit 94d08df into main Sep 29, 2026
18 checks passed
@Bushstar
Bushstar deleted the bush/atomic-operation-publication branch September 29, 2026 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants