You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched and didn't find an issue for this. I realize telegraf have recently (within the last 6 months) moved to Go dep. But is there interest for moving it yet again to go modules?
Proposal:
Use go modules instead of dep (and Godeps?) for managing/installing dependencies. For maintenance reasons, remove the old dependency files and update Makefiles to utilize them.
Requires the minimal supported Go version to be 1.11
Current behavior:
Uses dep (and Godeps?) for managing dependencies.
Use case: [Why is this important (helps with prioritizing requests)]
First of all, it's a lot faster for the number of dependencies required by telegraf to utilize go modules, especially while working with several check-outs:
Go modules appear to be faster at downloading dependencies.
Go modules holds a user-scoped cache of all dependencies, making it faster and more convinient to work with
Secondly, it doesn't require telegraf to be checked out into GOPATH, making it easeir to checkout and work with telegraf using multiple checkouts.
As a final small benefit, if working with a project that uses go modules, checking out a copy of telegraf within your application module (.e.g. as part of a Docker build-process), the main module won't dive into telegraf to look for dependencies, and won't run it's tests on go teset ./....
The text was updated successfully, but these errors were encountered:
We will consider this and likely make the change in the future but for now we still need support for building with Go 1.9 and we don't want to support two systems.
We will consider this and likely make the change in the future but for now we still need support for building with Go 1.9 and we don't want to support two systems.
Feature Request
I searched and didn't find an issue for this. I realize telegraf have recently (within the last 6 months) moved to Go
dep
. But is there interest for moving it yet again togo modules
?Proposal:
Use go modules instead of
dep
(and Godeps?) for managing/installing dependencies. For maintenance reasons, remove the old dependency files and update Makefiles to utilize them.Requires the minimal supported Go version to be 1.11
Current behavior:
Uses
dep
(and Godeps?) for managing dependencies.Use case: [Why is this important (helps with prioritizing requests)]
First of all, it's a lot faster for the number of dependencies required by telegraf to utilize
go modules
, especially while working with several check-outs:Secondly, it doesn't require telegraf to be checked out into GOPATH, making it easeir to checkout and work with telegraf using multiple checkouts.
As a final small benefit, if working with a project that uses go modules, checking out a copy of telegraf within your application module (.e.g. as part of a Docker build-process), the main module won't dive into telegraf to look for dependencies, and won't run it's tests on
go teset ./...
.The text was updated successfully, but these errors were encountered: