getsops / getsops/sops

Feature Request: General Caching

Open
#1,079 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
23.1k
Forks
1.1k
Avg merge
1d 11h
Merged PRs (30d)
9

Description

It would be great if SOPS could cache the keys it retrieves from services like GCP KMS and others.

In a git repository with hundreds of encrypted files, it takes forever to run a simple log search.

Contributor guide

Open the contributing guide

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.

Research direction

Start by tracing how SOPS retrieves keys from GCP KMS and other services during a log search. Determine the intended cache scope, lifetime, invalidation behavior, and handling of repeated key requests. Done should mean searches over repositories with many encrypted files avoid unnecessary key retrieval while preserving correct decryption.

Written by the indexing model from the issue text.

Assessment

Tech stack
gcp, go
Domain
cli, performance, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.