Secrets missing when a path contains both secrets and additional paths with secrets.

[obautista-clgx]

Hello,

I have a KV v2 structure like this in Vault v1.4.3:

secret
└── nonprd
└── wrong_org
└── wrong_ecosystem
└── app
├── myownpath
│   ├── test3
│   └── test4
├── test1
└── test2

Where:

• test[1,2] are secrets under folder 'app'
• myownpath is another folder under 'app'
• test[3,4] are secrets under folder 'myownpath'

Then I exported all secrets with vault-backend-migrator v0.2.1-dev:
./vault-backend-migrator -export secret/data/ -metadata secret/metadata/ -file all_secrets.json -ver 2

For some reason the secrets under secret/data/nonprd/wrong_org/wrong_ecosystem/app are missing in my output file and path secret/data/nonprd/wrong_org/wrong_ecosystem/app/myownpath is showing up twice:

{
"path": "secret/data/nonprd/wrong_org/wrong_ecosystem/app/myownpath",
"pairs": [
{
"key": "test3",
"value": "Mw=="
},
{
"key": "test4",
"value": "NA=="
}
]
},
{
"path": "secret/data/nonprd/wrong_org/wrong_ecosystem/app/myownpath",
"pairs": [
{
"key": "test3",
"value": "Mw=="
},
{
"key": "test4",
"value": "NA=="
}
]
},

The same happens if I set -export=secret/data/nonprd/wrong_org/wrong_ecosystem/ at extraction time:
./vault-backend-migrator -export secret/data/nonprd/wrong_org/wrong_ecosystem/ -metadata secret/metadata/nonprd/wrong_org/wrong_ecosystem/ -file wrong_ecosystem.json -ver 2

Is this a known limitation in vault-backend-migrator?
Is there a way to work around it?

Thank you