SMOODEV-1523: ESO bearer-token refresher#101
Merged
Merged
Conversation
…m SST deploy) ESO's webhook provider reads a static bearer from external-secrets/ smooai-config-bootstrap, but api.smoo.ai issues short-lived client_credentials JWTs (~1h) — so a static token goes stale and ESO sync silently 401s. That's why workload secrets are Pulumi-baked at SST deploy time (SMOODEV-1347), coupling every secret-value change to a ~1h platform deploy. Add @smooai/config/eso-refresher (bin smooai-config-eso-refresher): a sidecar that re-mints the token on a short interval via the same TokenProvider the SDK uses (invalidate + getAccessToken so the Secret always holds a near-full-TTL token) and patches it into the bootstrap Secret. ESO then always reads a fresh bearer; a 'th config set' goes live on ESO refresh + rollout restart, no deploy. Fail-loud initial sync (crash-loop on misconfig); loop failures logged+retried. K8s write behind a SecretWriter seam for unit testing (6 tests, no live cluster). Includes Dockerfile.eso-refresher + docs/ESO-Bearer-Refresher.md. Epic SMOODEV-1522. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: 2b96be3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
Problem
ESO's webhook provider reads a static bearer from `external-secrets/smooai-config-bootstrap`, but `api.smoo.ai` issues short-lived `client_credentials` JWTs (~1h). A static token goes stale → ESO sync silently 401s → that's why workload secrets are Pulumi-baked at SST deploy time (SMOODEV-1347), coupling every secret-value change to a ~1h platform deploy.
Solution
New `@smooai/config/eso-refresher` (bin `smooai-config-eso-refresher`): a sidecar that re-mints the token on a short interval via the same `TokenProvider` the SDK uses (invalidate + getAccessToken so the Secret always holds a near-full-TTL token) and patches it into the bootstrap Secret. ESO then always reads a fresh bearer; a `th config set` goes live on ESO refresh + rollout restart — no platform deploy.
Epic SMOODEV-1522 · part of the ESO restore (1524 generator, 1525 smooai wiring + MiMo validation).
🤖 Generated with Claude Code