Consider deprecating sops audit and replacing with documentation on using external tools
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
At Mozilla, we are currently only using sops audit for a very specific use case where it might make more sense to lean on something like the linux auditing framework to provide monitoring on file access to various sops-encrypted files.
There has been one indication that I'm aware of (https://github.com/mozilla/sops/issues/405) that sops users are using the audit functionality, so the other option would be to feature-freeze it and add documentation for using external tools as an addition.
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
Review the existing sops audit functionality and the usage report in issue #405, then compare the proposed Linux auditing framework and external-tool documentation options. Done means the project has a decided direction—deprecation, feature freeze, or retention—with the corresponding documentation scope identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100