Repository navigation
Name failing keys on the final line when config is invalid - #1256
Merged
Merged
Conversation
The last line of output now reads `💥 [varlock] Invalid env vars: A, B, +N more 💥`, capped at 5 keys / ~80 chars. Tools that only keep the tail of a failed process (k8s termination messages, systemd status) now show which vars to fix. CLI error summaries get a [varlock] prefix. Fixes #1246
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
varlock-website | b1ca563 | Commit Preview URL Branch Preview URL |
Oct 29 2026, 05:41 AM |
Contributor
|
The changes in this PR will be included in the next version bump.
|
Contributor
📦 Bundle size
dist/ only; native binaries are versioned separately and not counted here. |
![pullfrog[bot]](https://avatars.githubusercontent.com/in/1768019?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes: Reviewed the complete PR and traced invalid-config failures through the CLI handler.
- Failing-key summary:
InvalidEnvErrornames failing schema keys, caps the list by count and approximate length, and reports omitted keys with+N more. - CLI formatting: Invalid-config and
CliExitErrorsummaries now include[varlock], without changing validation, silent errors, or exit behavior. - Coverage and docs: Added formatter and final-line smoke coverage, and updated the usage example. The Varlock build, 20 focused unit tests, and direct
load/runCLI checks passed; the full smoke suite and website build were not run.
gpt-6.1-sol ｜ 𝕏
varlock
@varlock/astro-integration
@varlock/cloudflare-integration
@varlock/nextjs-integration
@varlock/nuxt-integration
@varlock/vite-integration
@varlock/native-helper-darwin
@varlock/native-helper-linux-arm64
@varlock/native-helper-linux-x64
@varlock/native-helper-win32-x64
@varlock/1password-plugin
commit: |
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 #1246. Thanks to the reporter for the clear write-up.
When config is invalid, the last line of output now names the failing keys:
The keys go on the final line rather than the top banner because that's what platforms actually surface: Kubernetes
FallbackToLogsOnErrorkeeps the last 80 lines / 2 KB, andsystemctl statusshows the last 10 lines. ECS, Cloud Run and CI annotations show no output at all. Key names come from the schema, never values.+N moreInvalidEnvError.messagecarries the same textCliExitError) now get a[varlock]prefix, matching the runtime errorsNot covered:
load --format json-full(used byauto-loadand the framework integrations) never throws, so it still prints no final summary line. That is tracked with the broader error-output review.