Skip to content

spurious warning when starting external provisioner with PSK #11307

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
spikecurtis opened this issue Dec 21, 2023 · 0 comments · Fixed by #11309
Closed

spurious warning when starting external provisioner with PSK #11307

spikecurtis opened this issue Dec 21, 2023 · 0 comments · Fixed by #11309
Assignees
@spikecurtis
Labels
s3 Bugs that confuse, annoy, or are purely cosmetic

Comments

@spikecurtis
Copy link
Contributor

When you start an external provisioner using a PSK the CLI drops a warning

check entitlement warnings error: get user me: GET http://coder.example.com/api/v2/users/me: unexpected status code 401: You are signed out or your session has expired. Please sign in again to continue.: Try logging in using 'coder login <url>'.

        Error: Cookie "coder_session_token" or query parameter must be provided.

This happens because the PSK auth doesn't work for the entitlement warnings or other startup checks.

We should just ignore these checks when starting an external provisioner daemon as they are meant for humans not a daemon.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@spikecurtis spikecurtis

Labels
s3 Bugs that confuse, annoy, or are purely cosmetic
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: stop printing warnings on external provisioner daemon command coder/coder
1 participant
@spikecurtis