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

kubebuilder update generates Gopkg.toml with hardcoded versions #419

Closed
alvaroaleman opened this issue Oct 7, 2018 · 6 comments
Closed
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@alvaroaleman
Copy link
Member

The kubebuilder update command currently generates a Gopkg.toml with hardcoded versions:

[[constraint]]
name="sigs.k8s.io/controller-runtime"
version="v0.1.1"
[[constraint]]
name="sigs.k8s.io/controller-tools"
version="v0.1.1"

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.

@droot
Copy link
Contributor

droot commented Oct 8, 2018

@alvaroaleman Though the version in the dep stanza is v0.1.1, dep will pick the v0.1.x where x being the latest patch version on v0.1.x (dep docs here). This is intentional because we want newly created Kubebuilder project to pick the latest stable version on 0.1.x of controller-runtime and controller-tools.

And if you want to update to new version to pick recent fixes on v0.1.x, you can run 'dep ensure -update sigs.k8s.io/controller-runtime`.

@alvaroaleman
Copy link
Member Author

alvaroaleman commented Oct 8, 2018

@droot I see, thanks for the clarification. I find that a little unintuitive tbh but that is obviously something on dep side.

Maybe we can change the lines to version="^v0.1.1" to make this more obvious?

@justinsb
Copy link
Contributor

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.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 26, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 26, 2019
@DirectXMan12
Copy link
Contributor

No longer using dep, closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

6 participants