Reset Content Store payload_version to 0 in non-prod envs
#2158
Conversation
This file contains 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
Occasionally, Content Store and Publishing API can fall out of sync in non-production environments after the environment sync process has completed. Content Store can be a day 'ahead' of Publishing API. Consequently, any publish events from Publishing API in the affected environment will be rejected by Content Store, if the `Event.maximum_id` in Publishing API is behind the `payload_version` of the `ContentItem` being updated in Content Store. The pragmatic fix is to reset the `payload_version` in Content Store so that it can never be ahead of Publishing API.
kevindew
approved these changes
Jul 8, 2024
brucebolt
approved these changes
Jul 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Occasionally, Content Store and Publishing API can fall out of sync in non-production environments after the environment sync process has completed. Content Store can be a day 'ahead' of Publishing API.
Consequently, any publish events from Publishing API in the affected environment will be rejected by Content Store, if the
Event.maximum_idin Publishing API is behind thepayload_versionof theContentItembeing updated in Content Store.The pragmatic fix is to reset the
payload_versionin Content Store so that it can never be ahead of Publishing API.Tested on Integration (via
k exec deploy/content-store -it -- rails db -pand running the query in the console).