getsops / getsops/sops

diff shows entire file has changed

Open
#1,480 2 comments 0 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

Hi! With recent upgrades sops 3.7.3 -> sops 3.8.1 (latest) we noticed that the whole file now is changed, even when changing a single key in YAML. However, the docs claim

https://raw.githubusercontent.com/getsops/sops/main/README.rst

  • diffs are meaningful. If a single value of a file is modified, only that
    value will show up in the diff. The diff is still limited to only showing
    encrypted data, but that information is already more granular that
    indicating that an entire file has changed.

Can you please share your understanding, is this a bug, or now it's an untended behavior?

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 comparing the reported behavior between sops 3.7.3 and 3.8.1, using the diff claims in README.rst as the expected behavior. Reproduce a one-key YAML change and determine whether the entire file or only the changed value appears in the diff. Done means the regression or intended behavior is documented with a clear explanation and reproduction result.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.