Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

fioan89
Copy link
Collaborator

@fioan89 fioan89 commented Sep 12, 2025

This was a regression for the custom flows that required authentication via certificates, the http client and the coder cli were properly initialized but afterward the token was still required for storing.

Note: the issue was hard to catch early on because the official coder cli is not supporting auth. via certificates.

This was a regression for the custom flows that required authentication via certificates,
the http client and the coder cli were properly initialized but afterward the token was
still required for storing.

Note: the issue was hard to catch early on because the official coder cli is not supporting auth. via certificates.
Poll jobs now have a random friendly name that changes each time
a new job is created, and the logging for when the jobs are created
or cancelled is also improved. The idea behind this commit is to improve
debugging sessions on client logs by:
- having clear log lines saying when a job is created/destructed
- easy to remember and cross-match job names (instead of cryptic java reference values)
@fioan89 fioan89 changed the title ffix: don't store token when certificates are configured fix: don't store token when certificates are configured Sep 12, 2025
Seems like we can't properly get the coroutine name from a Job.
The name of the coroutine is not super friendly but still workable with
the new logs.
Copy link
Member

@code-asher code-asher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me but was this causing a bug or something? Looks like it would just store a blank string in the secrets store which seems like it would essentially just be a no-op.

@fioan89
Copy link
Collaborator Author

fioan89 commented Sep 13, 2025

Looks good to me but was this causing a bug or something? Looks like it would just store a blank string in the secrets store which seems like it would essentially just be a no-op.

Yeap, it raised an error. Seems like the underlying store will not allow nu/empty values.
image

@code-asher
Copy link
Member

code-asher commented Sep 13, 2025

Trippy! Ohhh and I thought a blank value would call store.clear(key) but I see that storeTokenFor does not invoke set.

@fioan89 fioan89 merged commit 6b00191 into main Sep 13, 2025
6 checks passed
@fioan89 fioan89 deleted the fix-dont-store-token-when-auth-via-certificates branch September 13, 2025 10:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants