Import path not used

[blacs30]

In the Readme it looks like one can define the import path of the secrets but looking at the code it's clear that the path variable is unused.

It would be great if a different path could be used to import the secrets to.

[Lirt]

I noticed the same just after first import try.

I guess the import path should be inserted before path (there could be two slashes, so it needs to be handled somehow) in this part of code for each item.

[Lirt]

What would be more usable is that the path that is saved in JSON after export command will not contain the path specified in export command.

What I mean is:

vault-backend-migrator -ver 1 -export /my-directory/my-secrets/ -file secrets.json
cat secrets.json
{
  "data":
  [
    {
      "path":"secret1","pairs":[{"key":"value","value":"s1"}]
    },
    {
      "path":"secret2","pairs":[{"key":"value","value":"s2"}]
    },
    {
      "path":"nested-dir1/secret3","pairs":[{"key":"value","value":"s3"}]
    },
    {
      "path":"nested-dir2/secret4","pairs":[{"key":"value","value":"s4"}]
    },
  ]
}

Then I can run import to some path and all paths will be unpacked in it.

vault-backend-migrator -ver 1 -import /different-directory/my-secrets/ -file secrets.json
vault list /different-directory/my-secrets/
> secret1
> secret2
> nested-dir1/secret3
> nested-dir2/secret4