Caching decryption key from Azure Keyvault?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
We have a repo with several hundred secrets, all encrypted through SOPS. Through our CI, all these secrets have to be decrypted before we can work with them. It takes >5 minutes to decrypt them, as each decryption requires querying Azure.
Is there any way to cache the decryption key after the first decryption, so all following secrets encrypted with that key won't have to query AKV?
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
The issue names no source file, test, or entry point. Start by tracing SOPS's Azure Key Vault decryption path and how often it queries Azure during CI. Done means repeated secrets encrypted with the same key can be decrypted without repeated Key Vault queries, with behavior and security implications covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- cloud, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100