Tags: channable/vaultenv
Tags
v0.15.0 - "A token of my appreciation" This release adds two new authentication methods to Vaultenv: - GitHub authentication - Kubernetes authentication (thanks @ruuda!) The former is meant to be used in a development environment, and works with a personal access token. The latter is meant to be used in a Kubernetes cluster. This release also updates some dependencies.
v0.14.0 - "It's the little things" This release fixes some minor issues in Vaultenv: - Vaultenv will now enable "line buffering" mode for its output, which prevents issues with log messages getting mixed up or delayed if e.g. running under Systemd or Kubernetes. This was fixed by @ruuda in #115. - When printing the configuration with `--log-level info` Vaultenv will now correctly specify the unit for the base delay (milliseconds), where it previously printed an ambiguous plain number. This was added by @ruuda in #113. This release also contains fixes to make running the integration tests more reliable / work in more Linux environments. This was contributed by @ruuda in #114.
v0.13.1 - "Owned by me and not by thee" This release fixes a bug in the provided Debian package. The packages of 0.13.0 and earlier versions were not build with the `fakeroot` utility, which caused the installed package files (`/usr/bin/vaultenv` and `/etc/secrets.d/`) to be owned by the local user with uid 1000 instead of by `root`. We've now adjusted the build script to correctly use `fakeroot`, the package will also automatically correct this issue by changing the owner and mode of `/usr/bin/vaultenv` and `/etc/secrets.d` when upgrading from an earlier version. There are no changes to the code of the Vaultenv binary, except for an increase in the version number.
PreviousNext