-
Notifications
You must be signed in to change notification settings - Fork 16
Review Flux code duplication #4
Comments
Ok, maybe it's backwards and Flux could be using |
At least for the time being, we should attribute the code and make sure it's obvious where it came from. |
The code is (C) the Flux authors. |
So we're happy to vendor the flux code as-is as long as we can fix the TODOs that are there in the code, today this code have known issues with different edge cases for general, non-flux usage. The fork can/hopefully is temporary if flux can merge the patches that are needed. After the temporary fork/vendor of the code, upstream has changed, hence the diff above. cc @stealthybox |
The thing here is that we need a generic git library in the gitops toolkit, and what flux had worked almost, but not without some patching. One (possibly) good way to do this would be to use a "real" generic git library like https://godoc.org/gopkg.in/src-d/go-git.v4 instead |
@stefanprodan pointed out that some code of Flux made its way into
gitops-toolkit
. Could this be made a dependency instead?The text was updated successfully, but these errors were encountered: