Repository navigation
Conversation
The Golden Repo dropped this schedule on 2026-09-30 (pdq-deploy-inventory#94). Nine fleet repositories still carried its identical Monday 09:17 UTC cron, which GitHub fires hours late and all at once: about 56 vCPU of stacks against the account's 32-vCPU limit. On 2026-10-05 every Linux stack's scheduled run died at RunInstances with VcpuLimitExceeded. Here, all six scheduled runs since 2026-08-31 failed. The workflow now runs on pushes to protected main that match its path filter, and on manual dispatch; the header states those two triggers in the Golden Repo's words. aws-reaper.yml keeps its own quarter-hour schedule, so cleanup does not depend on this workflow's triggers.
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.
What
.github/workflows/aws-deploy.ymldrops itsscheduletrigger (Mondays 09:17 UTC). The workflow now runs on pushes to protectedmainthat match its path filter, and on manual dispatch.Why
The Golden Repo stopped its weekly run on 2026-09-30 (nwarila-platform/pdq-deploy-inventory#94). Eleven fleet repositories still carried the identical cron (corrected from "nine": secure-wazuh and aws-workspace-builder were missed by a local-checkout grep). GitHub fires them hours late (17:40–18:33 UTC rather than 09:17) and all at once: about 72 vCPU of stacks against the account's 32-vCPU limit. On 2026-10-05, every Linux stack's scheduled run failed at RunInstances with
VcpuLimitExceeded. Here, all six scheduled runs since 2026-08-31 failed.aws-reaper.ymlkeeps its own quarter-hour schedule, so cleanup does not depend on this workflow's triggers.Proof
main's file with exactly the two header lines replaced and the three schedule lines deleted (2 added, 5 removed); nothing else in the workflow changes.on:keys arepushandworkflow_dispatch.Merge order
Merging this triggers a deploy (the workflow is in its own path filter), so merge the CIS image bump #29 first: a deploy on the v07 pin fails at Terraform apply. Merge the fleet's deploy-triggering PRs one at a time; the stacks share the 32-vCPU limit.