Releases: Qarik-Group/safe
Safe v0.0.10
New Features
safe
now writes a small~/.svtoken
file for other
applications (like [Spruce][1]) to use without having to
understand the~/.saferc
file format.safe
now understands thevault
subcommand, allowing users to
hook up targets in~/.saferc
to thevault
cli.
Bug Fixes
safe
no longer requires the~/.vault-token
file to be set.safe
now correctly uses the tokens listed in~/.saferc
when
connecting to the targeted vault.
Safe v0.0.9
Bug Fixes
- Strip trailing newline from values read via normal prompts,
to ensure that LDAP authentication works properly.
Safe v0.0.8
New Features
- Targets -
safe
can now bounce between any number of
Vaults easily, without getting the wires crossed. - Authentication -
safe auth
now handles the authentication
against the Vault (using either token, Github or LDAP backends) - The new
safe env
sub-command exists to help troubleshoot
auth/targeting issues. - New
safe paste
sub-command is just likesafe set
, except it
never asks for confirmation of what you just pasted from
1password.
Safe v0.0.7
Bug Fixes
Fix versioning problem / Github Release issues in pipeline
Safe v0.0.6
New Features
- New
safe help
command to get help right there, in your
terminal! HT/@geofffranks
Safe v0.0.5
Test Release Notes (please ignore)
Safe v0.0.4
New Features
safe tree
now defaults to listing all of secret/
if no arguments are specified.
"Bug" Fixes
Concourse build pipeline fixed after upgrade to 0.74.0. :/
Safe v0.0.3
New Features
New tree
subcommand for printing a hierarchical listing of all
of the reachable paths.
New paths
subcommand for printing a flat listing of all of the
reachable paths (fully-qualified).
New export
and import
subcommands for exporting and
re-importing (bulk read / write) of entire subtrees, possibly from
different Vaults.
Safe v0.0.2
Enhancements
There is now a new prompt
sub-command that prints out messages.
It can be used in long pipeline chains to provide some direction to the
end user about what is coming next ("now enter RabbitMQ creds")
safe
now honors the $VAULT_SKIP_VERIFY
environment variable,
and will skip TLS certificate verification when so directed.
The set
operation now prints the "fixed" values to the screen, so that if
you call something like this:
safe set secret/creds username=opsadmin password
it will prompt for the password subkey after it has printed out that the
associated username is "opsadmin".
Bug Fixes
Terminating an interactive session now properly re-sets the ECHO
terminal property, so you can tell what you are typing again.
Safe v0.0.1
Initial Release
This is the first public release of safe, a Vault CLI.