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

feature: Expose logic to generate APIExport from APIResourceSchema #2133

Open
1 task done
hasheddan opened this issue Oct 5, 2022 · 2 comments
Open
1 task done
Assignees
Labels
area/apiexports kind/feature Categorizes issue or PR as related to a new feature.

Comments

@hasheddan
Copy link
Member

Feature Description

Currently, the apigen tool offers the useful functionality of generating an APIExport for each group in the set of APIResourceSchemas. This is after generating the APIResourceSchemas from CustomResourceDefinitions -- logic that is exposed to third parties in the apisv1alpha1 package.

Proposed Solution

It would be helpful to also expose the APIExport generation in the apisv1alpha1 package.

Alternative Solutions

The alternative today would be to let folks copy this logic around, or (hopefully not) programatically invoke the apigen tool.

Want to contribute?

  • I would like to work on this issue.

Additional Context

When this logic is moved, we should consume it in the apigen tool as well.

@hasheddan hasheddan added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 5, 2022
@hasheddan hasheddan self-assigned this Oct 5, 2022
@ncdc ncdc added this to kcp Oct 5, 2022
@ncdc ncdc moved this to New in kcp Oct 5, 2022
@nrb nrb moved this from New to Backlog in kcp Oct 18, 2022
@nrb
Copy link
Contributor

nrb commented Oct 18, 2022

@hasheddan Is this in progress?

@hasheddan
Copy link
Member Author

@nrb yep! Should have PR soon 👍🏻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/apiexports kind/feature Categorizes issue or PR as related to a new feature.
Projects
Status: Backlog
Development

No branches or pull requests

3 participants