-
Notifications
You must be signed in to change notification settings - Fork 408
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 request]use one repo to manage all api in OpenYurt #953
Comments
/assign @rambohe-ch @huiwq1990 |
@rambohe-ch: GitHub didn't allow me to assign the following users: huiwq1990. Note that only openyurtio members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Great move! |
@huiwq1990 I have created two new repos for managing OpenYurt api and OpenYurt client.
and i have added the following organization secrets for the corresponding repos:
please the above secrets in your pipeline. |
@rambohe-ch DO you mean: https://github.com/openyurtio/yurt-app-manager/tree/master/pkg/yurtappmanager/client sync to openyurt/client_golang I think it's better put all of them in one repo, as they are generated by same crd definition and used together. |
@huiwq1990 Yes, it's more convenient to put all of them in one repo, and we can optimize |
What would you like to be added:
I want to create a repo named
openyurtio/api
to manage all of the external API types of OpenYurt. and the api structure as following:and the relationship between directory and repo is:
Why is this needed:
as you known, there are several api repos in OpenYurt community, it's not convenient to import by other clients, and it's very hard to manage so many repos. the current api repos as following:
moreover, we have some other API definition in other repos, like raven-controller-manager and pool-coordinator.
others
by the way, in order to sync charts and api files from scattered repos, we will create the following two github secrets for each repo.
/kind feature
The text was updated successfully, but these errors were encountered: