Closed stampycode closed 6 years ago
Same thing here, and this is forcing us to go back to the CLI for uploading JSON.
Currently, every secret's value field is written as a string. Whether this should be classified as a bug or not is debatable, as text input fields should imply strings rather than magic.
Ideally I would like to change the secret writing process to be a json-centric text editor. #226 raised this concern first. As with basically every other feature I want to implement, I simply don't have time to do so. I will link this to the other issue and keep the existing one open for cleanliness. As always, pull requests are welcomed.
Bug report:
Vault version: v0.9.3
Goldfish version: v0.9.0
Operating system: Linux
Steps to reproduce:
Expected behaviour: Expected Goldfish to either prevent me from squishing my JSON object into a string, or to allow me to edit my JSON object.
Actual behaviour: Goldfish flattens my JSON object when I edit & save it.
This isn't a feature request per-se, Goldfish shouldn't be allowing me to deform my Vault secret without warning me that Goldfish will revert the object to a string.