-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
Unable to export a KV path due to a segmentation violation
#74
Comments
Hi @nkpetko |
It's a KV of the following for both: KEY -------- VALUE If anything else is needed please ask |
I get this error as well for many secrets, for example:
maybe null value is the problem? |
@liyaka I figured it may have been a null value issue, I have a few KVs in the release side that are null but none in the debug side. I will look into it a bit more. |
@nkpetko is there a chance it will be fixed any time soon? |
@liyaka if I can find the root issue, and also @jonasvinther pulls a PR I make then soon |
If we can verify that the issue is a |
@jonasvinther i did more tests, it is definitely the null issue - in all cases when i had at least one secret that had a null inside, i got this error. |
@liyaka and @nkpetko please give release 0.3.3 a spin. I think I have managed to handle the nil values now. At least it works for my test cases. |
@jonasvinther Thank you! will test it later today |
@jonasvinther Works like charm! Thanks again :) |
When attempting export a specific path on vault, it will throw the following error:
There are 2 paths that have data in them
/secret/teams/neteng/grid-service-v2/release
-- throws/secret/teams/neteng/grid-service-v2/debug
-- can be exported, despite it having the same KV layoutThe export command is as follows:
./medusa export secret/teams/neteng/grid-service-v2/release --address="https://chi1-vault.simulprod.com" --token="s.token" --format="json" --insecure
It can export /debug but no /release
If you need any more information, please ask
The text was updated successfully, but these errors were encountered: