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

Refactor tree handling outside of yaml and json stores #92

Closed
autrilla opened this issue Aug 19, 2016 · 1 comment
Closed

Refactor tree handling outside of yaml and json stores #92

autrilla opened this issue Aug 19, 2016 · 1 comment
Assignees
Milestone

Comments

@autrilla
Copy link
Contributor

autrilla commented Aug 19, 2016

Since we have to allow output formats different from the input ones (i.e., input yaml, output json), it would be easier to assume sops can only encrypt trees, as the Python version does. The Go version currently does not make such assumption and lets Stores do whatever they want, but by doing this, we'd need each store to create a function to port their data to and from every other store. It's easier to only support trees.

This way, the stores will only have to know how to load the tree, and dump the tree including the sops branch or not. They don't need to take care of encrypting themselves or decrypting.

@autrilla autrilla added this to the Go rewrite milestone Aug 19, 2016
@autrilla autrilla self-assigned this Aug 19, 2016
@autrilla
Copy link
Contributor Author

Partially fixed by 2077806; JSON still missing.

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

1 participant