tailscale / tailscale/tailscale-rs
tailscale: provide config/state via the API
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 61
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 22
Description
Currently, node state (such as keys) and configuration data is read from a JSON file that's read (or generated) on tailscale-rs startup. We want users to be able to store state and configuration data however they want, and provide this to tailscale-rs via the API.
Refactor such that config/state can be provided to tailscale-rs via the API, and implement a default file-based persistence implementation on top that can be easily replaced by a user's own persistence scheme, if desired.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing where tailscale-rs reads or generates the JSON state and configuration during startup, then inspect the API boundary described in the issue. Define the persistence seam around API-provided state and configuration while keeping a default file-based implementation. Done means callers can provide their own persistence scheme without removing the default file behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100