-
Notifications
You must be signed in to change notification settings - Fork 702
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
flux plugin: switch to using flux native data types instead of unstructured #4112
Comments
Just FYI, I did see what Antonio did with kapp_controller and I am hoping to take things a bit further and least in flux plugin. In kapp_controller there are constant conversions from unstructured to typed ( |
Excellent, that'd be great to be able to use a typed client without having to use the same client-go version as the upstream go lib (carvel/flux - that was what stopped us initially using the typed client for carvel, from memory, needing to update our own go.mod deps to match their version). |
flux plugin: switch to using flux native data types instead of unstructured vmware-tanzu#4112
…stead of unstructured #4112 (#4175) * first step towards issue flux plugin: switch to using flux native data types instead of unstructured #4112 * fix merge issues * minor fixes * attempt to remove cmd/apprepository-controller/vendor/k8s.io/code-generator from my PR * attempt #2 * fix go.sum * still fixing go.mod and go.sum after merge from upstream main * attempt to get the latest from cmd/apprepository-controller/vendor/k8s.io/code-generator * revert last change: didn't work * Antonio's feedback * refactored clientgetter so that we can add more different client getters to it without breaking existing code
still work to do... |
…s instead of unstructured vmware-tanzu#4112 (part 1)
…finish flux plugin: switch to using flux native data types instead of unstructured #4112 (#4238) * attempt #2 * fix for httpclient library SetClientTLS cleanup + unit tests #4119 plus a couple unrelated unit test clean up items in flux plugin * remove most files from PR to see if passes CI end-2-end tests * add files back into PR, as they seem to have no effect on CI * remaining work for flux plugin: switch to using flux native data types instead of unstructured #4112 (part 1) * flux plugin: switch to using flux native data types instead of unstructured #4112 (part 2) * flux plugin: switch to using flux native data types instead of unstructured #4112 (part 3) * flux plugin: switch to using flux native data types instead of unstructured #4112 (part 5) * flux plugin: switch to using flux native data types instead of unstructured #4112 part 5 * minor fixes
Documenting leftover items for flux plugin per Pepe's request so we can prioritize it against other work
This is a leftover item from #3899
@antgamdia said:
Not now, but perhaps we can use the typed struct instead of dealing with the unstructured data directly (as I'm doing in the kapp plugin).
This has been on my TODO list for a while. To be clear. The benefit to end user is none. But the benefit to developers/maintainers of this code is huge. Code based on unstructured types is difficult to work with/maintain and is error prone. Not to mention very verbose.
Ideally, I'd want to switch to use APIs like https://github.com/fluxcd/source-controller/tree/main/api/v1beta1 which should make the code much more concise and easier to read.
The text was updated successfully, but these errors were encountered: