Repository navigation
Fix retention to use secondary - #108
Merged
Merged
Conversation
Collaborator
Author
|
I admit it's a bit bloated, we can remove the dry run once this is rolled out. |
Darkheir
approved these changes
Oct 12, 2026
Collaborator
Most of the complexity comes from the dry run part :) |
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
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.
Description
Add an env variable to control if the retention is based on the primary or secondary QW_RETENTION_TIMESTAMP_MODE
How was this PR tested?
Unit tests and will use dry run to double check