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
I have vault backed by consul which I am migrating to filesystem for backup purposes.
If my vault kv has a key named foo and a folder named _foo... both want to become _foo on the filesystem so I get a _foo is a directory error when running vault-migrator.
Since vault is okay with foo and _foo, is there some way to configure the consul file backend to make it handle this case? Do you have any advice that isn't: "don't do that, silly!" :-)
My config.json for vault-migrator --config config.json:
hi @jar349, not much to say. my only suggestion is to name differently keys and folders. is unfortunate that you have that issue, the script only has a job to copy the keys. unfortunately, I have not much time available to fix any incompatibility between backends.
I have vault backed by consul which I am migrating to filesystem for backup purposes.
If my vault kv has a key named
foo
and a folder named_foo
... both want to become_foo
on the filesystem so I get a_foo is a directory
error when running vault-migrator.Since vault is okay with
foo
and_foo
, is there some way to configure the consulfile
backend to make it handle this case? Do you have any advice that isn't: "don't do that, silly!" :-)My config.json for
vault-migrator --config config.json
:The text was updated successfully, but these errors were encountered: