-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
kubebuilder update
generates Gopkg.toml with hardcoded versions
#419
Comments
@alvaroaleman Though the version in the dep stanza is And if you want to update to new version to pick recent fixes on |
@droot I see, thanks for the clarification. I find that a little unintuitive tbh but that is obviously something on Maybe we can change the lines to |
I would +1 to changing this. I'm using go modules, and it's confusing to have a version specified in Gopkg.toml that isn't actually what you intend to use. |
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-testing, kubernetes/test-infra and/or fejta. |
No longer using dep, closing |
The
kubebuilder update
command currently generates aGopkg.toml
with hardcoded versions:kubebuilder/cmd/vendor/sigs.k8s.io/controller-tools/pkg/scaffold/project/gopkg.go
Lines 147 to 153 in 0f8f2d8
This is made worse by the fact that this is below a header
# STANZAS BELOW ARE GENERATED AND MAY BE WRITTEN - DO NOT MODIFY BELOW THIS LINE.
which makes it look like end-users should not touch that part.The text was updated successfully, but these errors were encountered: