fix: Make 'cloudflared access token' return with a non-zero exit code when token has expired #1429
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.
I've been working on a helper script for a project that automatically fetches an access token and updates a local
.env
file with the token. Sometimes the script would fail to detect thatcloudflared
failed to fetch a token by looking at its exit code.I needed to add the
[ -z "$token" ]
test to catch these cases.Looking at
cloudflared
's source, my guess is the command prints an empty token and exits with zero whenGetAppTokenIfExists
detects that the token has been expired and there was no error removing the file that the token was saved to.cloudflared/token/token.go
Lines 435 to 438 in 3f6b1f2