ci(rebuild-qa): add force-publish input to re-seed Option B ContentCurrent (QA) - #2062
Merged
Merged
Conversation
Release 1.20.0 → PROD
…rrent (QA) Mirrors rebuild-content.yml's force-publish. Needed to re-seed the QA ContentCurrent after the delta flags were toggled (a normal delta publish skips unchanged slugs vs ContentFiles, leaving ContentCurrent stale). One-time seed tool; recurring QA rebuilds dual-write deltas normally when WRITE is on.
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.
Why
rebuild-content-qa.ymlpublished QA content with no way to force a full republish, so a normal delta publish skips slugs unchanged vsContentFiles— leaving the QAContentCurrenttable stale after the Option-B read/skip flags are toggled (island hashes go out of date → QA tutorials would 404 on their islands). The main channel'srebuild-content.ymlalready has aforce-publishinput; QA lacked the parity.What
force-publishboolean workflow_dispatch input (default false).--forcetopublish-content.ts --channel qawhen set, so ALL slugs are published/dual-written — the one-time seed/repair path for QAContentCurrent.Context
Used tonight (dispatched from this branch) to re-seed the QA
ContentCurrentafter the fast-path flags were re-enabled ontutorials-srv-qa. Recurring QA rebuilds don't need it — they dual-write deltas normally when the write flag is on. Companion to the DB-config fix (#2061) and issue #2060.