tailscale / tailscale/go-cache-plugin
Support a read-only mode
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 81
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
It would be great to have an option to run in a "read-only" mode, where the cache plugin reads from S3, and stores the cache entries locally on disk, but does not attempt to write any data back to S3.
This feature might be useful in untrusted environments to prevent cache poisoning attacks.
I would suggest to add a new boolean flag --read-only, which defaults to false (keeping the current behavior). Similarly to MinUploadSize this would just skip the upload step.
If you agree with this proposal, I can also contribute this feature
Contributor guide
No contributing guide indexed for this repository
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 locating the MinUploadSize option, the --read-only flag parsing, and the S3 upload step. Trace how cache entries are read and stored locally, then verify that read-only mode skips uploads while the default behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100