sniptt-official/snip

🔐 A simple developer-friendly CLI for managing secrets

snip's Issues

Alternative: dotenv-vault

If you're looking for an alternative to this check out: https://github.com/dotenv-org/dotenv-vault

Sniptt was a cool project that I used to use. But as it stop being maintained, I had to look elsewhere. Didn't really find much so me and some friends starting building dotenv-vault.

Simple flag to have machine-readable `snip get` output.

Use-case being that if I adopt snip as a team with a shared vault, I'd want to call snip from scripts and retrieve a secret in plaintext.

For now the best option I found to get plaintext output of a secret value is:

snip get foo -q -o /dev/stdout

A convention of lots of programs would be to accept - in place of stdout to shorten the command.

A different option could be to implement a flag like snip get foo -r (-r/--raw for raw output mode).

Add os matrix to test workflow

We should use a matrix strategy with different OS versions when running the test jobs, similar to the node versions matrix.

Port CLI to Golang

It makes sense to port snip to golang, improving the overall DX and aligning with how we've built ots

Homebrew installation instructions on the website should have you tap the tap instead of installing it

The install instructions at https://www.sniptt.com/ have you run brew install sniptt-official/tap which will fail with the error Warning: No available formula or cask with the name "sniptt-official/tap". However if the instructions are updated to brew tap sniptt-official/tap the instructions work as expected.

Command line arg parsing not work properly when I want to add a password (using hidden text)

snip add joebloggs_aws_password_prod -v aws_initial_passwords

snip add joebloggs_aws_password_test --vault aws_initial_passwords

Also, moving the --vault not work either, nor adding the value as non-hidden text at the end.

snip --vault aws_initial_passwords add joebloggs_aws_password_test 1234
Error: Unknown argument: 1234
Hint: Use the --help option to get help about the usage

Setting or seeing a profile as context

Currently when I create a new profile it's not set as default. During command executions I also do not see what the profile is. As a result if I leave the --profile flag from the command I get errors that are quite strange and misleading. It would be good to:

• either set a default profile and see it on command executions
• or have some warnings / potential fixes with errors like: Are you running against the correct profile?

Listing empty vault seems fishy

samsavage@CVX-0032:/tmp snip ls --vault datauniverse_vault
✔ Fetching existing vault memberships
✔ Fetching vault secrets
Secret Name Owner

It looks like the vault contains 1 secret called Secret Name Owner but I don't think that is the intension.

If the vault is empty, no text should be output, or it should say "vault empty" or something.