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
If vault response data is josn, the safe get result should be json But the value is changed to string. Is it possible to support json format?
Here is response data field example
{"data":{"date":"2018-12-23T09:51:10.839Z","json":{"desc":"test"}}}
but result is below.
{"data":{"date":"2018-12-23T09:51:10.839Z","json":"{"desc":"test"}"}}
Thanks.
The text was updated successfully, but these errors were encountered:
For the not-so-keen observers like myself, the path key "json" is being set to an unescaped stringified version of its actual JSON payload: "{"desc":"test"}"; the inner quotes should have been escaped but are not, although the deeper problem is that the Vault API allows arbitrary nested structures and the safe CLI operates as if all values are opaque strings. Our compromise was to stringify the JSON.
I.e., you should be able to do this:
safe get secret/what/ever:json | jq -r .desc
and get "test".
Can you provide some steps (starting with a clean vault, or at least an unused path) to get into the state you are seeing, so that we can follow along and replicate / reproduce the exact issue, locally?
If vault response data is josn, the safe get result should be json But the value is changed to string. Is it possible to support json format?
Here is response data field example
{"data":{"date":"2018-12-23T09:51:10.839Z","json":{"desc":"test"}}}
but result is below.
{"data":{"date":"2018-12-23T09:51:10.839Z","json":"{"desc":"test"}"}}
Thanks.
The text was updated successfully, but these errors were encountered: