kebandClaude Opus 5.5
6fab41703e
Release / Build and publish (push) Successful in 22s
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
76 lines
2.8 KiB
Markdown
76 lines
2.8 KiB
Markdown
# SOPS and .env files in git repos
|
|
|
|
lazysecrets shows git repositories under **Repos**: their
|
|
[SOPS](https://github.com/getsops/sops)-encrypted files (YAML, JSON,
|
|
`.env`, INI) and plain env files as vaults, and the keys in them
|
|
(`db.password`, `list[0]`) as secrets.
|
|
|
|
## Which repos
|
|
|
|
**Repos** lists every repo with secret files under the `roots` (`~/git`
|
|
by default; one or two levels down, `repo` or `org/repo`), any listed in
|
|
`paths`, and any you starred something in (the repo, a file or a key),
|
|
wherever it is. They're checked in the background.
|
|
|
|
Started inside a repo, that repo gets a row of its own at the top,
|
|
`Repo · <name>`, and lazysecrets opens on it, with the files under the
|
|
directory you started in first. In the flat list (`` ` ``) it sorts first, marked
|
|
`· here`.
|
|
|
|
A repo without secret files isn't listed. `--dir <path>` starts somewhere
|
|
else, for example in one project of a monorepo.
|
|
|
|
Repos load themselves as they're found, files and keys, since they're
|
|
local and cheap: [Go to](keys.md#go-to) searches them without loading
|
|
anything by hand.
|
|
|
|
## Which files
|
|
|
|
**Env files**: `.env`, `.env.local`, `prod.env` and the like, also when
|
|
git-ignored (as they usually are), in the folders git tracks files in;
|
|
not `.env.example`, `.sample`, `.template` and the like. They're read
|
|
directly; a file with SOPS metadata is always treated as SOPS, whatever
|
|
its name.
|
|
|
|
Folders of dependencies and caches are never looked in, tracked or not:
|
|
`node_modules`, `vendor`, `.venv`, `venv`, `__pycache__`, `.terraform`,
|
|
`.gradle`, `.yarn`, `.next` and the like.
|
|
|
|
**SOPS files**: those tracked by git, then the first of
|
|
|
|
1. `include`/`exclude` in the repo's own `.lazysecrets.yaml` (committed,
|
|
so everyone sees the same files),
|
|
2. `include`/`exclude` in the config,
|
|
3. where the repo's `.sops.yaml` `creation_rules` say SOPS files go,
|
|
4. the whole repo.
|
|
|
|
`include`/`exclude` apply to env files too.
|
|
|
|
```yaml
|
|
providers:
|
|
repos:
|
|
roots: [~/git] # folders of repos (the default; [] turns it off)
|
|
paths: [~/work/infra] # single repos elsewhere
|
|
include: ["secrets/**", "**/*.sops.yaml"] # globs from the repo root; ** for any depth
|
|
exclude: ["**/testdata/**"]
|
|
```
|
|
|
|
## Decrypting
|
|
|
|
Listing never decrypts: SOPS encrypts values only, so keys and metadata
|
|
(encryption, last modified) are read straight from the files. Revealing,
|
|
copying or `lazysecrets get` decrypts one value with your `sops` binary, so
|
|
whatever sops uses works (age keys, Azure Key Vault through az, AWS/GCP
|
|
KMS, PGP). When sops can't decrypt, its whole error message is shown.
|
|
|
|
## Links
|
|
|
|
Links name the repo by its git remote, so they open in a colleague's clone
|
|
wherever it is:
|
|
|
|
```
|
|
lazysecrets://repo/git.example.com%2Fteam%2Finfra/secrets%2Fapp.yaml/db.password
|
|
```
|
|
|
|
See [links](links.md).
|