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

Selectively build API groups? #77

Open
nightkr opened this issue Oct 2, 2020 · 1 comment
Open

Selectively build API groups? #77

nightkr opened this issue Oct 2, 2020 · 1 comment

Comments

@nightkr
Copy link
Contributor

nightkr commented Oct 2, 2020

k8s-openapi compiles very slowly. That isn't really a dig on it, it's just a big crate.

But it would be nice if we could opt in to which APIs are actually relevant.

I figure a decent first approximation would be to have a cargo feature per apiVersion, which are already used for module separation anyway.

@Arnavion
Copy link
Owner

Arnavion commented Oct 2, 2020

It's not impossible, though it will require the codegen process to keep track of cross-module dependencies. Eg everything depends on meta/v1, so enabling anything else should also enable the meta/v1 feature. (Well, meta/v1 will need to be enabled by default anyway because of how fundamental it is, but you get the idea.)

Also, the feature names will have to incorporate the whole path so that they're unambiguous, eg apimachinery/pkg/api/resource -> "apimachinery_pkg_api_resource"

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

2 participants