Skip to content

gcloud-cli-health-check v3.2.0: SSO reauth + config-set workaround#20

Open
msmobileapps wants to merge 1 commit into
mainfrom
gcloud-healthcheck-lessons-20260421-2223
Open

gcloud-cli-health-check v3.2.0: SSO reauth + config-set workaround#20
msmobileapps wants to merge 1 commit into
mainfrom
gcloud-healthcheck-lessons-20260421-2223

Conversation

@msmobileapps

Copy link
Copy Markdown
Contributor

Summary

Auto-generated from the 2026-04-21 Cowork+DC health check run. Four new lessons surfaced; plugin updated to v3.2.0.

  • SSO reauth lessonopsagents.agency Workspace invalidates refresh tokens periodically, causing silent scheduled-run failures with Reauthentication failed. cannot prompt during non-interactive execution. Now step 8 in AUTO-FIX LOOP (manual fix flagged).
  • gcloud config set <property> workaroundconfig set tries to refresh the active account token on load, so it fails end-to-end when the primary token is blocked. Fix: switch to a working credentialed account, set the property, switch back. Now step 9 in AUTO-FIX LOOP.
  • Stale project references — all 14 occurrences of opsagent-491114 in SKILL.md replaced with opsagent-prod (SKILL.md had drifted from the v3.0.0 CLAUDE.md).
  • Account Architecture table rewritemsmobileapps@gmail.com has no IAM on opsagent-prod; socialjetopsagent is an active OpsAgent runtime project (hosts opsagent-core, opsagent-ai-runtime, opsagent-dashboard) not just SocialJet ops.

Test plan

  • After Michal runs gcloud auth login michal@opsagents.agency + gcloud auth application-default login, re-run the gcloud-cli-health-check scheduled task.
  • Verify the new step-c/region/project checks all target opsagent-prod (no stale opsagent-491114 references trigger).
  • Confirm the SKILL.md AUTO-FIX LOOP step 9 unblocks region fix in a future blocked-token scenario.

🤖 Generated with Claude Code running as Cowork scheduled task gcloud-cli-health-check.

…stale project fixes

From the 2026-04-21 Cowork+DC health check run.

New lessons documented in plugins/gcloud-cli-health-check/CLAUDE.md:
- opsagents.agency Workspace SSO invalidates gcloud refresh tokens on a
  schedule, causing silent scheduled-run failures with "Reauthentication
  failed. cannot prompt during non-interactive execution."
- gcloud config set <property> fails when the active account's refresh
  token is blocked, because it tries to refresh the token on load.
  Workaround: temporarily switch to another credentialed account, set the
  property, switch back. Now standard step 9 in the SKILL.md AUTO-FIX LOOP.
- msmobileapps@gmail.com has no IAM on opsagent-prod -- it only applied
  to the legacy opsagent-491114 project. Account architecture table fixed.
- socialjetopsagent is running opsagent-core, opsagent-ai-runtime, and
  opsagent-dashboard Cloud Run services alongside SocialJet + MyClaimPros
  -- it is an active OpsAgent runtime project, not just secondary ops.

SKILL.md changes:
- version 1.1.0 -> 1.2.0
- All opsagent-491114 references -> opsagent-prod (14 occurrences)
- New auto-fix steps 8 (SSO reauth detection) and 9 (config-set workaround)
- Account Architecture Reference rewritten to reflect current truth

Source: gcloud-health-check-2026-04-21.md run report.
@MichalOpsAgents

Copy link
Copy Markdown
Contributor

CTO review (2026-05-11): blocked on 1 failing CI check — Validate gcloud-cli-health-check from the Validate Plugin PR workflow. SOSA checks are all green. Worth a quick look at the validator log; if it's a transient false-positive, rerun the job. Otherwise fix and push.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants