-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Ability to turn off mutating main.go
when adding apis/webhooks
#1724
Comments
main.go
main.go
when adding apis/webhooks
Hi @christopherhein, Thank you for raise that. It shows related to the issue #932. See the comment #932 (comment). In this way, it shows blocked until we are able to have the plugin phase 2 implemented to know how better we could address this scenario. |
We discussed it in the bug triage meeting and then, was really decide that we might wait for the plugin phase 2 as well. |
Sounds good, thanks @camilamacedo86 ! |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Rotten issues close after 30d of inactivity. Send feedback to sig-contributor-experience at kubernetes/community. |
@fejta-bot: Closing this issue. 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. |
It would be nice to be able to set in the
PROJECT
that you didn't want the scaffolding to updatemain.go
this would allow scaffolding to work for projects that move their scheme/controller initialization to another directory likecmd/
. Today this still works properly if you are using it tocreate api
but when you usecreate webhook
it will fail and none of the files are created properly.RFE was requested from conversations in #1719
/kind feature
The text was updated successfully, but these errors were encountered: