Repository navigation
feat(config): support mounted secret _FILE values (#436) - #1238
Open
harshitethic wants to merge 1 commit into
Open
harshitethic wants to merge 1 commit into
harshitethic wants to merge 1 commit into
Conversation
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
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.
Fixes #436. Read CONCORD_RPC_HEADERS_FILE and CONCORD_GOOGLE_CLIENT_SECRET_FILE as alternatives to inline secrets, trimming one trailing newline (including CRLF). Reject conflicting direct/file settings and unreadable paths with errors that do not expose secret contents. Recognize both in the unknown-setting diagnostics and document them in .env.example. Two regression tests cover both secrets, warnings, malformed/conflicting input. Targeted Vitest, API typecheck and ESLint passed locally.