chore: replace official Civo API client by an internal API client #2584
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, we cannot update to the latest version of
github.com/civo/civogobecause it has dependencies on k8s.The k8s dependencies are intricate inside the official client, I didn't find an easy forking automation to remove the dependencies.
It's useless to depend on the official client because we cannot follow it, so we will not be able to get bug fixes.
We can use a thin client based on the API documentation.
I did the migration step by step (one commit per step):
DNSProviderby using the new mock system and using data from the API documentation to create fixture files.Each step/commit works (build and tests); there is no partial state to ensure no regression.