You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All 4 failures are the Push API Image job on push to main (runs 38622097744, 38640432809, 38644983626, 38646965219). Each fails at docker push with:
IAM Service Account Credentials API has not been used in project 922040293304 before or it is disabled β denied: Unauthenticated request ... artifactregistry.repositories.uploadArtifacts
Before #600, this job was "green" only because the Authenticate to Google Cloud step failed (invalid_target β WIF pool/provider missing) and continue-on-error: true skipped the push. No image has actually been pushed in the monitored window. Now that the WIF provider resolves, SA impersonation fails because iamcredentials.googleapis.com is disabled in broodly-491920.
Scope
This is a GCP project configuration gap, not a code defect. The repo change documents the missing API enablement prerequisite in the manual GCP setup guide; the fix itself requires a project owner to run it once.
The implementation for issue #607 is durable: commits are pushed and a pull request is open. This record is backed by verifiable artifacts you can confirm in one click.
Review happens on the PR. Acceptance criteria and test results are evidenced by the PR's diff and CI checks β not asserted here. If a later stage fails, this claim is retracted in place.
Activity
don-petry commentedon Oct 15, 2026
Dev-Lead Implementation Plan
Issue: #607 β [Fleet Monitor] combsmith/broodly β .github/workflows/ci.yml
Root cause
All 4 failures are the
Push API Imagejob onpushtomain(runs 38622097744, 38640432809, 38644983626, 38646965219). Each fails atdocker pushwith:Before #600, this job was "green" only because the
Authenticate to Google Cloudstep failed (invalid_targetβ WIF pool/provider missing) andcontinue-on-error: trueskipped the push. No image has actually been pushed in the monitored window. Now that the WIF provider resolves, SA impersonation fails becauseiamcredentials.googleapis.comis disabled inbroodly-491920.Scope
This is a GCP project configuration gap, not a code defect. The repo change documents the missing API enablement prerequisite in the manual GCP setup guide; the fix itself requires a project owner to run it once.
Required manual action (project owner)
gcloud services enable iamcredentials.googleapis.com sts.googleapis.com iam.googleapis.com artifactregistry.googleapis.com --project=broodly-491920Then re-run the latest failed
CIrun onmain.Implementation Checklist
infra/terraform/GCP_SETUP.md: add a "1.0 Enable Required APIs" step before WIF setupTests to Write
Push API Imagejob after the API is enabled.Test Command
bash .dev-lead/scripts/dev-lead-lint.sh(repo lint); no code changes.don-petry commentedon Oct 15, 2026
Dev-Lead: Implementation Complete β PR #608
The implementation for issue #607 is durable: commits are pushed and a pull request is open. This record is backed by verifiable artifacts you can confirm in one click.
acd64b3562b78225ce43e405ca458da978f91e98main: 1 file(s), +13/-0 linesReview happens on the PR. Acceptance criteria and test results are evidenced by the PR's diff and CI checks β not asserted here. If a later stage fails, this claim is retracted in place.
feat: implement issue #607 β [Fleet Monitor] combsmith/broodly β .gitβ¦