Check declared credentials at launch, not at compile - #91
Merged
Merged
Conversation
Compiling writes only the variable names into task.toml and compose, so the compiler's insistence that every value be set forced VERO_SKIP_SECRET_CHECK onto every compile-only use and placeholder keys onto CI. The check moves to vero harbor run, after the env file is loaded and before anything is compiled or spent. The flag is gone from the compiler, eleven documents and the CI workflow. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
Summary
vero harbor buildused to refuse to compile unless every credential a build declares was present in the environment, even though compiling writes only the variable names into task.toml and compose. Every compile-only use (preflight, CI, tests, docs) therefore carriedVERO_SKIP_SECRET_CHECK=1, and CI exported placeholder keys to satisfy it.vero harbor run, after the env file is loaded and before anything is compiled or spent. Same message, same guard, at the one place the values are consumed.VERO_SKIP_SECRET_CHECKis gone from the compiler, the docs (11 files) and the CI workflow's placeholder env.Verification
tests/test_v05_harbor_build.py,tests/test_v05_cli.py,tests/test_v05_harbor_http.pyandtests/test_v05_benchmark_configs.pypass withOPENAI_API_KEYandOPENAI_BASE_URLunset.🤖 Generated with Claude Code
The PR appears safe to merge; the credential check is placed at the supported launch boundary without changing generated credential routing.
Summary
Diagram
%%{init: {'theme': 'neutral'}}%% flowchart LR A[Load env file] --> B[Resolve build parameters] B --> C[Load and validate config] C --> D[Collect declared credential names] D --> E{All values present?} E -->|No| F[Fail before compilation or spend] E -->|Yes| G[Preflight models] G --> H[Compile temporary Harbor task] H --> I[Transform gateway environment] I --> J[Launch Harbor] K[Compile-only build] --> L[Emit placeholders without credential values]Reviews (1) · Last reviewed commit: "Check declared credentials at launch, no..."