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
Support JSON arrays of arrays #640
Comments
nilium
added a commit
to nilium/sops
that referenced
this issue
Mar 9, 2020
Add support for decoding JSON arrays of arrays by handling, during slice decoding, when the next token is an array opening. This produces nested []interface{} slices. Closes getsops#640.
nilium
added a commit
to nilium/sops
that referenced
this issue
Mar 9, 2020
Add support for decoding JSON arrays of arrays by handling, during slice decoding, when the next token is an array opening. This produces nested []interface{} slices. Closes getsops#640.
nilium
added a commit
to nilium/sops
that referenced
this issue
Mar 9, 2020
Add support for decoding JSON arrays of arrays by handling, during slice decoding, when the next token is an array opening. This produces nested []interface{} slices. Closes getsops#640.
autrilla
pushed a commit
that referenced
this issue
Mar 20, 2020
Add support for decoding JSON arrays of arrays by handling, during slice decoding, when the next token is an array opening. This produces nested []interface{} slices. Closes #640.
Fixed with #642 |
rochaporto
pushed a commit
to rochaporto/sops
that referenced
this issue
Jun 22, 2020
Add support for decoding JSON arrays of arrays by handling, during slice decoding, when the next token is an array opening. This produces nested []interface{} slices. Closes getsops#640.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, JSON arrays of arrays cannot be parsed by sops, leading to an unmarshaling error. Given the following input, for example:
{ "ary": [[]] }
sops will produce the following error:
The same input treated as YAML works, so the current workaround at least appears to be to use YAML.
The text was updated successfully, but these errors were encountered: