You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, this action requires someone to update the TAILSCALE_AUTHKEY every 90 days, which is easy to forget. Is there a way we can automate this process?
Searching around, I've come across a few statements hinting at automation becoming possible soon:
We updated these labels to be less confusing a little while back. The labels no longer say that keys never expire, since all our keys expire after 90 days for security reasons.
If this bug was about that confusion, we can consider it fixed. If this bug was about the fact that our keys expire after 90 days, then we can discuss that. We have plans to build systems for automated key renewal, but they're not ready yet.
We're working on a way to generate auth keys via our public API. Once that's ready, you could combine that with the GitHub CLI and run a cron job like:
gh secret set TS_KEY --org=organization-name --body "your auth key"
But I'm not sure if these have materialized, or if there was some other recommended best practice that can ensure our GitHub actions will continue to work well without a manual renewal process.
The text was updated successfully, but these errors were encountered:
Right now, this action requires someone to update the TAILSCALE_AUTHKEY every 90 days, which is easy to forget. Is there a way we can automate this process?
Searching around, I've come across a few statements hinting at automation becoming possible soon:
tailscale/tailscale#1151 (comment)
https://www.reddit.com/r/Tailscale/comments/pcpn0k/using_ts_in_github_actions/
But I'm not sure if these have materialized, or if there was some other recommended best practice that can ensure our GitHub actions will continue to work well without a manual renewal process.
The text was updated successfully, but these errors were encountered: