fix: keep optional provider credentials from blocking cloud startup - #12
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
A fresh Linux cloud run verified all eight tools and shared command files, but could not launch because optional provider credentials were unavailable during setup. Default setup now reports those missing credentials without blocking independent work. Explicit --require-environment retains strict task preflight; tool and dependency failures still block.
All17 regressions pass. Actual Cockpit default returns0 and strict mode returns2 with missing credentials. Fresh cloud session verification follows publication.
Post-Deploy Monitoring & Validation
Codex will check a fresh session during this audit. Expect tool checks and session launch, with provider credentials reported unavailable where appropriate. Restore the saved setup if launch still fails; never treat a launched session as proof of provider access.