generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 28
feat: add retry workflow for uninstallable packages #1809
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
cdklabs-automation
merged 18 commits into
main
from
mrgrain/feat/retry-uninstallable-packages
Nov 21, 2025
Merged
feat: add retry workflow for uninstallable packages #1809
cdklabs-automation
merged 18 commits into
main
from
mrgrain/feat/retry-uninstallable-packages
Nov 21, 2025
+2,890
−252
Conversation
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
Add a new state machine that allows operators to retry processing of all uninstallable packages with a single button click. The workflow reads the uninstallable packages report, triggers reprocessing for each package, and updates the inventory report. Changes: - Add RetryUninstallablePackages state machine - Add retry button to backend dashboard - Update operator runbook with troubleshooting guide - Wire inventory canary into orchestration
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
88f5f84 to
a256f2b
Compare
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
aemada-aws
reviewed
Nov 21, 2025
aemada-aws
approved these changes
Nov 21, 2025
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.
Adds a one-click workflow for operators to retry processing of all uninstallable packages. When packages fail to install during documentation generation, they're tracked in a report but previously required manual intervention for each package.
What Changed
New State Machine:
RetryUninstallablePackages- Reads the uninstallable packages report from S3, triggers the existingReprocessDocumentationPerPackageworkflow for each entry, handles failures gracefully, and runs an inventory update after completion.Dashboard Integration - Added "Retry Uninstallable Packages" button to the backend dashboard overview and as a primary action button on the uninstallable packages report widget.
Operator Documentation - New troubleshooting section covering investigation steps for missing package documentation, including uninstallable packages, corrupt assemblies, and transliteration errors. Documents the retry workflow and expected behavior.
Why This Matters
Before: Operators had to manually trigger reprocessing for each uninstallable package individually, which was time-consuming and error-prone when dealing with multiple packages.
After: Single button click retries all uninstallable packages automatically, with clear documentation about expected behavior and potential alarms.
Expected Behavior
When triggered, the workflow may cause temporary alarms (
Orchestration/Resource/ExecutionsFailedandOrchestration/DLQ/NotEmpty) as some packages may still fail on retry. The inventory report updates incrementally via the scheduled canary, so changes may take a few hours to fully reflect in the dashboard.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license