adjust to repository v1.8 eventlog shape#61
Open
hugowetterberg wants to merge 2 commits into
Open
Conversation
since repository v1.8.0 an ACL update that accompanies a document version is carried on the document event's acl field instead of being emitted as a standalone acl event. Apply it to the update request in real-time mode; catch-up mode keeps reading the current ACL from document meta for new documents.
elephant-api to v0.23.1, elephantine to v0.27.1, newsdoc to v1.1.0, pgx to v5.10.0, urfave/cli/v3 to v3.9.0, and the golang.org/x group.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
documentevents to target updates. Since elephant-repository v1.8.0 (Implicit ACL events elephant-repository#595), an ACL update that accompanies a document version — including every document creation — is carried on thedocumentevent'saclfield instead of being emitted as a standaloneaclevent. The real-time path relied on those standalone events, so against a v1.8+ source it would replicate new documents and versions without their ACLs. Catch-up mode is unchanged: it keeps reading the current ACL from document meta for new documents, which is more authoritative than the historical event ACL.aclevents (ACL-only updates, archive restores) are still emitted by the repository and remain handled as before.