Skip to content

v1.1.0 — persist access & refresh tokens under ~/.tf/

Choose a tag to compare

View all tags
@LordGameleo LordGameleo released this 02 Jul 11:48
v1.1.0
34730a5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's new

  • Token persistence to files. The setup binary now writes the obtained access token (JWT) and refresh token to separate files, stored under a ~/.tf/ directory in the logged-in user's home (created 0700, files 0600).
  • New flags:
    • --access-token-file (default ~/.tf/access-token)
    • --refresh-token-file (default ~/.tf/refresh-token)
  • Paths are forwarded through the sudo/scheduled-task re-exec, so tokens are written in the logged-in user's session. Defaults resolve against the user's home, and the ~/.tf/ directory is created automatically if missing.

Notes

  • Default token location moved from ~/.tfy-refresh-token to ~/.tf/refresh-token. Machines with a cached token at the old path will do one fresh device login on next run.
  • Enables downstream integrations (e.g. aitori browser governance) to read the same gateway token.

Binaries for macOS (arm64/amd64), Linux (amd64), and Windows (amd64) are attached.

Assets 6
Loading