getsops / getsops/sops

output does not include a newline at end of file

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

Hello! Just a small nit, hope it's alright.

sops' output does not include a newline at the end of it's output, which is not in accordance with POSIX's definition of a Text File.

sops -e --age $age foobar.json | tail -c 1
}

Thanks!

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 running the reported sops -e --age $age foobar.json | tail -c 1 command and trace the CLI output path responsible for the final byte. Done means encrypted output ends with a newline while preserving the existing output behavior; verify this with the same command and POSIX text-file expectation.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.