DOC-373: Fix broken Update Parity Docs pipeline - #854
Merged
Conversation
Since the localstack-pro CI restructure (PR #7263, June 2026), the parity-metric-* artifacts are only uploaded by scheduled nightly runs of the 'AWS / Build, Test, Push' workflow, while push-triggered runs (the vast majority) only execute acceptance tests. The artifact search window of 20 runs therefore no longer contained any run with parity metrics. Raise the search window (LIMIT) to 200 runs so the latest successful nightly run is found. Also remove the download step for the Free Plan K8s pipeline: the 'AWS / Community K8S tests' workflow was deleted from localstack-pro in the same restructure, so its artifacts no longer exist.
HarshCasper
requested review from
quetzalliwrites and
remotesynth
as code owners
August 10, 2026 11:48
Deploying localstack-docs with
|
| Latest commit: |
421c895
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://62470887.localstack-docs.pages.dev |
| Branch Preview URL: | https://doc-373-fix-broken-update-pa.localstack-docs.pages.dev |
remotesynth
approved these changes
Aug 10, 2026
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.
Motivation
Fixes DOC-373.
The Update Parity Docs pipeline has been failing since mid-June (e.g. this run), so the implementation/parity coverage on service pages stopped updating.
Root cause is the CI restructure in localstack-pro (PR #7263, merged June 2, 2026):
AWS / Build, Test, Pushruns the full integration suite (which uploads theparity-metric-pro-raw-amd64-*/parity-metric-raw-amd64-*artifacts) only onscheduleevents — push-triggered runs only execute acceptance tests. The fetch script (get_latest_github_metrics.shfromlocalstack/meta) scans only the last 20 successful runs of the workflow, and with ~12 push runs/day that window no longer reaches any nightly run. The pipeline kept working until mid-June only while pre-restructure runs remained inside the 20-run window.AWS / Community K8S testsworkflow was deleted from localstack-pro in the same restructure, so theparity-metric-community-k8s-integration-raw-*artifacts can never be found again.Changes
LIMIT: 200(env already supported by the fetch script) on the two parity-metric download steps so the artifact search window reaches the latest successful nightly run (currently at index ~26 of the successful-run window; 200 gives ~3 weeks of margin). The success-only filter is deliberately kept: failed nightlies upload incomplete parity artifacts (e.g. missing matrix groups), which would silently understate coverage.AWS / Community K8S tests), since the upstream workflow no longer exists.create_data_coverage.pypicks up test sources by CSV filename prefix, so the absence of these files is harmless.The other steps need no changes:
capture-notimplemented*artifacts are still uploaded on every main-branch run, andAWS / Pro K8S testsruns nightly with regular successes.Testing
Ran
get_latest_github_metrics.shlocally withLIMIT=200for both previously-failing steps — both located the latest successful nightly run (Aug 5) and downloaded all 8 test-group CSVs each, producing the expectedpro-integration-test-*/community-integration-test-*files intarget/metrics-raw.After merging, the fix can be verified by manually dispatching the Update Parity Docs workflow.