We can definitely improve on this, but in the short term, the token returned by the cli-auth lasts 7 days. It will be refreshed if it's used at least once in that 7 day time period. So you can get the token from /cli-auth on your user, or some machine user you made. And put that token into your CI/CD.

You can use the token in the cli directly, and not use coder login. In github actions you can use the coder cli to upload the templates using the cli flags.

coder --token <token> --url https://coder.deployment.com template ...

You can also use env vars:

CODER_SESSION_TOKEN=<token> coder --url https://coder.deployment.com template ...

Or write straight to the session file in ~/.config/coderv2/session and ~/.config/coderv2/url

Thanks for submitting the issue! I edited the description a bit so we can use this to track creating tokens and some docs around using Coder in CI.

Thanks for the quick response! I didn't realize that the token in the browser is actually the access token 😉 Great product by the way 😊

@ghuntley brought up an interesting point that we should consider before we add long-lived tokens. We may want to consider generating tokens in a searchable format so they can be picked up in security scans: https://docs.github.com/en/code-security/secret-scanning/about-secret-scanning

@ghuntley brought up an interesting point that we should consider before we add long-lived tokens. We may want to consider generating tokens in a searchable format so they can be picked up in security scans: https://docs.github.com/en/code-security/secret-scanning/about-secret-scanning

Also adding the convention into projects such as:

• https://github.com/awslabs/git-secrets
• https://github.com/Yelp/detect-secrets

• Token management/revocation will be an OSS feature
• Down the road, we may add enterprise functions such as configurable token durations and custom scopes

We also have this requirement for pushing templates via Github actions. We're actually looking at something that can just keep templates in sync as they're updated. E.g. point coder at a repo revision of templates and it just takes care of it.

@f0ssel thanks for the implementation! Is there any possibility to generate the token from the UI?

Opening up #5409