-
Notifications
You must be signed in to change notification settings - Fork 928
chore: explain GIT_ASKPASS behavior in docs #12784
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.
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
Conversation
- VSCode configuration requirements
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
huge. thank you @Emyrk
docs/admin/external-auth.md
Outdated
@@ -212,8 +212,32 @@ you can require users authenticate via git prior to creating a workspace: | |||
|
|||
 | |||
|
|||
The following example will require users authenticate via GitHub and auto-clone | |||
a repo into the `~/coder` directory. | |||
### `GIT_ASKPASS` will auto-refresh tokens |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think users will be unfamiliar with what GIT_ASKPASS
is.
We should approach this from a git
perspective... as the tool most users are familiar with, and explain that we use GIT_ASKPASS
is a variable Git hooks into for authentication.
It's worth mentioning that coder external-auth token <id>
will output the same token as the Git hook will.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will update.
command only works if inside
Note: Some IDE's override the `GIT_ASKPASS` environment variable and need to be | ||
configured. | ||
|
||
**VSCode** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should note that this is automatically done for you. No manual user configuration is actually needed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is not automatically done though. The user must manually turn off the VSCode overrides.
Does our extension do this for you?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See this issue: #12291
Closes #12291