allow loading of other k8s API implementations #45
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.
Refactor to move all code generated from swagger spec into a separate module, named
ApiImpl
.KuberContext
now optionally takes a module reference to load APIs from. It defaults to the one bundled in Kuber.jl -ApiImpl
, but can be replaced with a different module whenKuberContext
is constructed. This will let Kuber.jl be used with code generated for a different Kubernetes API version, or for a spec with custom APIs (e.g. for CRDs).Custom CRDs will need some more generalization of the code generator. Will do that in a separate PR.