kubebuilder
kubebuilder copied to clipboard
kubernetes-sigs
[WIP] :sparkles:: Adding ability to re-scaffold existing projects
Closes #2068
Relevant discussion
Description
Add tooling to help migrate existing projects to newer versions of scaffolding.
Hi @rumstead. Thanks for your PR.
I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
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.
@camilamacedo86 / @joelanford (sorry for tagging you so much camilamcedo86 I just read the "don't tag in comments or commits"), looking for guidance here. If we want to reuse the functions that init, create, edit, etc us, we cannot put the command in the alpha package. Thoughts on how to proceed?
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: rumstead
Once this PR has been reviewed and has the lgtm label, please assign varshaprasad96 for approval by writing /assign @varshaprasad96 in a comment. For more information see:The Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@rumstead: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| pull-kubebuilder-e2e-k8s-1-19-16 | dfb999cb646d2d532324417d7d43a3ef76a027d3 | link | false | /test pull-kubebuilder-e2e-k8s-1-19-16 |
| pull-kubebuilder-e2e-k8s-1-20-7 | dfb999cb646d2d532324417d7d43a3ef76a027d3 | link | false | /test pull-kubebuilder-e2e-k8s-1-20-7 |
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.
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. I understand the commands that are listed here.
@camilamacedo86 before I go and write tests I wanted to get your take on the structure, flow, and approach.
@rumstead: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| pull-kubebuilder-e2e-k8s-1-19-16 | dfb999cb646d2d532324417d7d43a3ef76a027d3 | link | false | /test pull-kubebuilder-e2e-k8s-1-19-16 |
| pull-kubebuilder-e2e-k8s-1-20-7 | dfb999cb646d2d532324417d7d43a3ef76a027d3 | link | false | /test pull-kubebuilder-e2e-k8s-1-20-7 |
| pull-kubebuilder-e2e-k8s-1-26-0 | 460aeb6e327f5d201a527fc0d6c9882f725bab23 | link | true | /test pull-kubebuilder-e2e-k8s-1-26-0 |
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.
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. I understand the commands that are listed here.
HI @rumstead,
We created a design proposal doc to move forward with this one. See: https://github.com/kubernetes-sigs/kubebuilder/issues/3244
Also, we decide to apply this one for the GS0C 2023. If accepted, a student can work on this and move forward with the work you began to try to address.
So, I hope you do not mind if we close this one. Who will be able to work on this one will still able to check this PR and see how we can use it to help out move forward. Please, feel free to reach out via slack if you need.
Hey @camilamacedo86 I think you should add gsoc label if this is reserved for gsoc participants.
