SOPS should recogonize .env.* files as DOTENV filetype
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
When using something such as dotenv-flow in react/node projects you can load various environments in env files named for example .env.development, .env.stage etc.
SOPS will recognize .env and filename.env as a DOTENV file but not .env.something. Is there a way to make sops treat files prefixed with .env.* as DOTENV filetype without having to specify input/output type on command line every time?
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
Start by tracing SOPS's existing detection for .env and filename.env files, then identify the entry point that assigns the DOTENV filetype. Confirm how .env.* names are handled and add coverage for representative environment suffixes. Done means those files are recognized as DOTENV without specifying input or output types on the command line.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100