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
It'd be nice if vaulted load could import and overwrite/merge passed values when the target vault already exists instead of nuking the existing vault and recreating it. Here's my use case:
I have a front end that allows users to configure the contents of the vault. Previously this modified a dot file, now it modifies the vault. In order to maintain this functionality I have to do the following:
use vaulted dump to dump the vault to memory (prompt user for vault password)
prompt user for keys
use jq to insert keys into vault JSON in memory
use vault load to recreate the vault. (prompt user to create vault password)
obviously this leaves some room for error as it might not be obvious to the user that the vault is being recreated, and at best it's a lot of password prompts. If load supported import/merge the workflow would look like this:
prompt user for keys
insert keys into vault with vault load (prompt user for vault password)
For my specific case I don't care if an existing key in a vault is overwritten with a new value (as that's what's happening now anyways).
The text was updated successfully, but these errors were encountered:
It'd be nice if
vaulted load
could import and overwrite/merge passed values when the target vault already exists instead of nuking the existing vault and recreating it. Here's my use case:I have a front end that allows users to configure the contents of the vault. Previously this modified a dot file, now it modifies the vault. In order to maintain this functionality I have to do the following:
vaulted dump
to dump the vault to memory (prompt user for vault password)jq
to insert keys into vault JSON in memoryvault load
to recreate the vault. (prompt user to create vault password)obviously this leaves some room for error as it might not be obvious to the user that the vault is being recreated, and at best it's a lot of password prompts. If load supported import/merge the workflow would look like this:
vault load
(prompt user for vault password)For my specific case I don't care if an existing key in a vault is overwritten with a new value (as that's what's happening now anyways).
The text was updated successfully, but these errors were encountered: