Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migration to and from filesystem can have issues with underscores #6

Open
jar349 opened this issue Aug 7, 2018 · 2 comments
Open

Comments

@jar349
Copy link

jar349 commented Aug 7, 2018

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:

$ cat backup.json
{
    "to": {
        "name": "file",
        "config": {
            "path": "/Users/jar349/projects/vault-backups/data"
        }
    },
    "from": {
        "name": "consul",
        "config": {
            "address": "localhost:8500",
            "path": "vault/"
        }
    }
}
@criloz
Copy link
Member

criloz commented Aug 7, 2018

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.

@jar349
Copy link
Author

jar349 commented Aug 8, 2018

In your opinion, where should a fix for this be made? Here, or in the consul file backend implementation?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants