From 8fad8338e615c50dd30cbe007b8b9b730678be1e Mon Sep 17 00:00:00 2001 From: Bharat Kathi Date: Fri, 5 Jun 2026 01:57:32 -0700 Subject: [PATCH] fix(argocd): point OIDC at the new Sentinel client_id MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The previous client (XwwQhdCWZ9Cn) lived in the sentinel Postgres database that got wiped during the gr-postgres recreate. Re-registering the ArgoCD app in Sentinel post-recovery produced a fresh auto-generated client_id (b9OrCRXdo1VQ). The matching clientSecret is rotated in the argocd-sentinel-oidc k8s Secret out-of-band — see the module's main.tf header comment. --- infra/environments/prod/main.tf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/infra/environments/prod/main.tf b/infra/environments/prod/main.tf index b504e9c..4f0a885 100644 --- a/infra/environments/prod/main.tf +++ b/infra/environments/prod/main.tf @@ -45,7 +45,7 @@ module "argocd" { domain = "argocd.gauchoracing.com" # Sentinel-generated client_id for the registered ArgoCD application. - oidc_client_id = "XwwQhdCWZ9Cn" + oidc_client_id = "b9OrCRXdo1VQ" depends_on = [module.eks] }