Feature: Cache Tailscale credentials

Open
#146 1 comment 8 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
32/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions, typescript
Domain
ci-cd, networking

Research direction

No files, tests, or entry points are named. Locate the TypeScript action entry point and trace how credentials are obtained and used; then clarify the cache boundary, user-defined key behavior, and credential-validity check. Done means valid cached credentials can let workflows continue during a Tailscale coordination outage without mixing credentials between workflows.

Written by the indexing model from the issue text.

Description

needs-triage

When tailscale's systems are having an outage, this causes an immediete disruption to anyone using this action to get their CI on their tailnet.

This action can cache the credentials used in the past (possibly with a user defined cache key so we don't have workflows using each others credentials). If the credentials are still valid, then we would remove a strong dependency on the coordination server.

Dominant language
TypeScript
Stars
938
Forks
137
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tailscale/github-action

All issues in tailscale/github-action

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.