chore: wire JWT_SECRET into tes service - #21
Merged
Conversation
TES's authentication now goes through omnibioai-iam-client (see omnibioai-tes's TES IAM integration PR), which needs JWT_SECRET for its HS256 fallback verification path -- same var name/value every other JWT_SECRET consumer in this file already uses. IAM_URL/REDIS_URL were already wired for tes.
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.
Summary
JWT_SECRET: \${AUTH_SECRET_KEY:-change-me}to thetesservice's environment -- same var name/value every otherJWT_SECRETconsumer in this compose file already uses.IAM_URL/REDIS_URLwere already wired fortes.omnibioai-iam-client, which needs this secret for its HS256 fallback path (RS256/JWKS is the primary path and doesn't need it, but a migration window means both must keep validating).Test plan
origin/main-- isolated, single-file change