fix: Cleaner error when not authenticated and token file is missing#366
Merged
Conversation
disq
requested review from
erezrokah and
murarustefaan
and removed request for
a team
stoovon
approved these changes
Jun 19, 2026
erezrokah
approved these changes
Jun 19, 2026
kodiakhq Bot
pushed a commit
that referenced
this pull request
Jun 24, 2026
🤖 I have created a release *beep* *boop* --- ## [1.14.11](v1.14.10...v1.14.11) (2026-06-19) ### Bug Fixes * Cleaner error when not authenticated and token file is missing ([#366](#366)) ([e559cba](e559cba)) * Generate CloudQuery Go API Client from `spec.json` ([#364](#364)) ([c9fbe79](c9fbe79)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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
3 participants
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.
When no token file exists (user never ran
cloudquery login),GetTokennow returns a concise "not authenticated" message instead of leaking the wrappedos.ReadFileerror (failed to read refresh token: failed to read file: open …/cloudquery/token: no such file or directory); genuine read errors still surface verbosely.Currently, the error message from
cloudquery switchright aftercloudquery logout: