feat: repos with SOPS and .env files in --demo
Three repos, the first as the one lazysecrets was started in: encrypted YAML, JSON and dotenv files, a gitignored .env, a tracked one in red and an untracked one, with each file's details. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
b530c043f7
commit
7bc9834f05
4 files changed
+146
-13
No files matched your search
@@ -4,27 +4,22 @@ A terminal UI for finding, reading and sharing secrets. Inspired by the fantasti
|
||||
|
||||
## Main features
|
||||
|
||||
- **Read-only**: lazysecrets never creates, changes or deletes a secret, so
|
||||
it's safe to point at production. That's by design and may stay that way.
|
||||
(`e` opens a repo's SOPS or `.env` file in your editor, or `sops edit`;
|
||||
any change is yours.)
|
||||
- **Read-only**: lazysecrets never creates, changes or deletes a secret.
|
||||
That's by design and may stay that way.
|
||||
- **Zero setup**: uses the logins you already have (`az`, the Databricks
|
||||
CLI, `sops`, `git`). No config file needed.
|
||||
- **Search everything**: `ctrl+s` searches every source at once, with
|
||||
fzf-style matching (`'exact`, `^prefix`, `suffix$`, `!not`), and jumps
|
||||
straight to the result.
|
||||
- **Share links**: `s` copies a `lazysecrets://` link. A colleague opens it
|
||||
fzf-style matching.
|
||||
- **Share links**: Share `lazysecrets://` links with colleages. A colleague opens it
|
||||
with their own access, from the terminal or with a click in the browser
|
||||
or chat.
|
||||
- **Careful with values**: values stay hidden until you reveal them, and
|
||||
copied values are cleared from the clipboard after 30 seconds.
|
||||
- **Scriptable**: `lazysecrets get <link>` prints a value for scripts and
|
||||
pipes.
|
||||
- **Favourites**: star the secrets you use most and get back to them in one
|
||||
key.
|
||||
- **Favourites**: star the secrets you use most for easy access.
|
||||
- **Expiry warnings**: secrets, keys and certificates that expire soon are
|
||||
marked, listed together in the status pane, and `lazysecrets expiring`
|
||||
checks every vault from a pipeline.
|
||||
marked, listed together in the status pane.
|
||||
- **Your way**: rebind any key, pick a theme, and add custom commands to run
|
||||
on a secret.
|
||||
- **Try it first**: `lazysecrets --demo` runs on built-in sample data.
|
||||
|
||||
Reference in new issue
Block a user