Vaultenv Alternatives

Similar projects and alternatives to vaultenv

nixpkgs

973 15,656 10.0 Nix vaultenv VS nixpkgs

Nix Packages collection & NixOS
nix

372 10,879 10.0 C++ vaultenv VS nix

Nix, the purely functional package manager
InfluxDB

www.influxdata.com sponsored

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
asdf

340 20,448 7.9 Shell vaultenv VS asdf

Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
sops

150 15,069 9.2 Go vaultenv VS sops

Simple and flexible tool for managing secrets
nickel

46 2,127 9.5 Rust vaultenv VS nickel

Better configuration for less
rfcs

49 488 5.0 vaultenv VS rfcs

The Nix community RFCs (by NixOS)
aptly

17 2,509 7.7 Go vaultenv VS aptly

aptly - Debian repository management tool
WorkOS

workos.com sponsored

The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
haskell-nix

6 1,127 2.7 Nix vaultenv VS haskell-nix

Nix and Haskell in production
robotnix

14 562 6.8 Nix vaultenv VS robotnix

Build Android (AOSP) using Nix [maintainer=@danielfullmer,@Atemu]
nixos

7 102 8.6 Nix vaultenv VS nixos

Discontinued NixOS Configuration (by pimeys)
nix-1p

7 860 4.7 Nix vaultenv VS nix-1p

A (more or less) one page introduction to Nix, the language.
nixos

19 159 9.3 Nix vaultenv VS nixos

My NixOS Configurations
rosdistro

6 879 10.0 Python vaultenv VS rosdistro

This repo maintains a lists of repositories for each ROS distribution
pndev

1 14 4.9 Rust vaultenv VS pndev

CLI tool for es-development
nix-ros-overlay

3 165 9.0 Nix vaultenv VS nix-ros-overlay

ROS overlay for the Nix package manager
rclcpp

4 487 8.9 C++ vaultenv VS rclcpp

rclcpp (ROS Client Library for C++)
ros2nix

1 17 0.0 Nix vaultenv VS ros2nix

Use ROS with the Nix package manager
nix-home

1 5 6.6 Nix vaultenv VS nix-home

Nix + HM = <3 (by pwm)
SaaSHub

www.saashub.com sponsored

SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better vaultenv alternative or higher similarity.

Suggest an alternative to vaultenv

vaultenv reviews and mentions

Posts with mentions or reviews of vaultenv. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-08-16.

Using secrets in kube prom stack helm chart
2 projects | /r/devops | 16 Aug 2021

Having secrets in an external system (like Hashicorp Vault) and then using [vaultenv](https://github.com/channable/vaultenv) to inject these during `helm install/upgrade`. So you end up with something like `vaultenv ... -- helm install --set config.myvar=${VAULTENV_INJECTED_ENV_VALUE}` (or similar). Point is I use vaultenv to run helm with secrets injected as env vars only during the helm run, and use helm's `--set` flag to set individual secrets. This can get tedious if you have many secrets as you have to specify each of them individually with --set. Usually I wrap this in a Makefile or a shell script for easier invoking.
Nix is the ultimate DevOps toolkit
21 projects | news.ycombinator.com | 9 Apr 2021

> Also, regarding DevOps, the tooling around Nix makes it a little brittle for anything event based--rapidly changing configurations on the fly due to network conditions (Consul, Ansible, etc). This is where configuration management is heading, and due to the static nature of Nix, delegating dynamic changes is hard/anti pattern.
Channable uses Consul, Vault, etc. for dynamic configuration and it works with Nix just fine.
You don't have to use static configuration files with Nix. Either fetch dynamic stuff using the Consul, Vault, etc. APIs at runtime or use a tool like vaultenv [1] or similar if you don't want this logic in your application code.
Put those tools in your systemd service before launching your app, and you're good to go.
(NB: I was DevOps teamlead at Channable while a part of this work was being done. Sad that I won't be able to see the final picture.)
[1]: https://github.com/channable/vaultenv