You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
safe locally should do what safe local does, but (a) always use memory-backing, (b) not muck about with ~/.saferc, (c) not block and (d) continue parsing commands.
safe export --to-disk should export the contents of the given tree (or secret/) to disk, turning path components into directories, and keys into files containing their respective values.
This would finally let me use safe x509 to build out the complicated mess of mutual TLS certificates that BOSH and Cloud Foundry require without spinning up a Vault and having to multi-process. safe local works great for interactive use, but in a one-shot scripting scenario like this, leaves much to be desired.
The text was updated successfully, but these errors were encountered:
I would really like to be able to do this:
There's a bit to unpack here:
safe locally
should do whatsafe local
does, but (a) always use memory-backing, (b) not muck about with~/.saferc
, (c) not block and (d) continue parsing commands.safe export --to-disk
should export the contents of the given tree (orsecret/
) to disk, turning path components into directories, and keys into files containing their respective values.This would finally let me use
safe x509
to build out the complicated mess of mutual TLS certificates that BOSH and Cloud Foundry require without spinning up a Vault and having to multi-process.safe local
works great for interactive use, but in a one-shot scripting scenario like this, leaves much to be desired.The text was updated successfully, but these errors were encountered: