envconsul
sops
Our great sponsors
envconsul | sops | |
---|---|---|
4 | 150 | |
1,993 | 15,114 | |
0.4% | 2.7% | |
5.9 | 9.0 | |
3 months ago | 5 days ago | |
Go | Go | |
Mozilla Public License 2.0 | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
envconsul
- Ask HN: Developers/DevOps, how do you manage environment variables?
-
Can one use Vault to inject environment variables needed to setup on stack up rather than saving them in environment files with docker-compose?
Might not perfectly fit but I think that was one of the ideas behind - https://github.com/hashicorp/envconsul (which can use Vault as a source), and probably to a degree consul-template (though a quick skim of the documentation and I'm not sure if can use Vault as a source.)
-
How to Handle Secrets on the Command Line
You have envchain to store secrets as ENV variables in your keyring and execute commands:
https://github.com/sorah/envchain
Not really something you would use for production web apps, I think envconsul covers that usecase:
https://github.com/hashicorp/envconsul
-
To those who have set up some kind of automatic deployment of their services on pushes to a git repo, how do you manage environment variables/.env files?
Have you looked into Hashicorp's consul + envconsul? You can also encrypt data using their vault.
sops
-
Pico.sh – Hacker Labs
My script just sets up default .sops.yaml for https://github.com/getsops/sops
You can further edit .sops.yaml(eg have multiple of them) and decide how you split secrets in your directory tree to further customize who can decrypt the secrets.
It works pretty well for prod/dev splits, etc
-
Encrypting your secrets with Mozilla SOPS using two AWS KMS Keys
Mozilla SOPS (Secrets OPerationS) is an open-source command-line tool for managing and storing secrets. It uses secure encryption methods to encrypt secrets at rest and decrypt them at runtime. SOPS supports a variety of key management systems, including AWS KMS, GCP KMS, Azure Key Vault, and PGP. It's particularly useful in a DevOps context where sensitive data like API keys, passwords, or certificates need to be securely managed and seamlessly integrated into application workflows.
-
An opinionated template for deploying a single k3s cluster with Ansible backed by Flux, SOPS, GitHub Actions, Renovate, Cilium, Cloudflare and more!
Encrypted secrets thanks to SOPS and Age
-
Tracking SQLite Database Changes in Git
We do the exact same thing to keep track of some credentials we use sops[1] and AWS KMS to separate credentials by sensitivity, then use the git differ to view the diffs between the encrypted secrets
Definitely not best practice security-wise, but it works well
[1] https://github.com/getsops/sops
-
The Twelve-Factor App
For anyone new to SOPS like I was - https://github.com/getsops/sops
- Storing and managing private keys
-
Show HN: Shello – Wrangle Environment Variables
I've found this is largely solved by strictly separating plain config and secrets, and then having secrets pull from GCP secret manager / vault / whatever.
You can then commit all the config (including the secret identifiers) and it all just works so long as you're authenticated with your secret storage system.
We do this for the live configuration as well in line with Gitops and find it to work well.
If you don't want to use a cloud secret manager you can also use something like https://github.com/getsops/sops to commit the encrypted secrets safely
-
Check your secrets into Git [video]
Basically, the simpler the better --just encrypt your secrets and check them in to version control.
We use SOPS[0] for this, and have found it to be pretty nice.
[0]: https://github.com/getsops/sops
-
How to secure secrets of docker-compose stacks with git?
The answer is that secrets shouldn't be stored in the git repo at all, but somewhere safe like a password manager or Mozilla's SOPS which people seem to love.
-
Is it safe to commit a Terraform file to GitHub?
Unfortunately, the SOPS project is in some sort of a limbo state and there has been quite a long period with limited maintenance and unclear position from Mozilla. Despite the project being accepted into the CNCF, it's still unclear what will happen with it going forward.
What are some alternatives?
zsh-secrets - Storing GPG encrypted environment variables
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
s6-overlay - s6 overlay for containers (includes execline, s6-linux-utils & a custom init)
Vault - A tool for secrets management, encryption as a service, and privileged access management
selfhosted - docker compose + traefik + tailscale
age - A simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composability.
envchain - Environment variables meet macOS Keychain and gnome-keyring <3
git-crypt - Transparent file encryption in git
platform-compat - Roslyn analyzer that finds usages of APIs that will throw PlatformNotSupportedException on certain platforms.
terraform-provider-sops - A Terraform provider for reading Mozilla sops files
ShellCheck - ShellCheck, a static analysis tool for shell scripts
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.