Skip to content
This repository has been archived by the owner on Oct 21, 2022. It is now read-only.

Dependency management: (try to) use 'go mod' as replacement for 'go dep' #125

Open
ionysos opened this issue May 22, 2019 · 3 comments
Open
Assignees
Labels
enhancement New feature or request

Comments

@ionysos
Copy link
Contributor

ionysos commented May 22, 2019

Description

Starting in Go 1.13, module mode will be the default for all development.

I think we should try to port our solution with the current use of dep to mod as dependency management.

User Story

As Go(Lang) developer I want to use Go internals in order to discard third-party extensions.

Implementation idea

Try to delete dep dependent files and to create mod required files.

@ionysos ionysos added the enhancement New feature or request label May 22, 2019
@ionysos ionysos self-assigned this May 22, 2019
@ionysos
Copy link
Contributor Author

ionysos commented Jun 3, 2019

go-mod branch shows the PoC but, unfortunately, this will lead to a tremendously increased docker image build time because go modules cache need to be warmed up each & every time. This was already discussed at golang/go#26610. If we want to use the discussed go mod download command solution we have to re-think our current build process. Otherwise, this won't lead to better results.

@ialidzhikov
Copy link

You can use -mod=vendor which will use the vendor/, not the go modules cache.

@ionysos
Copy link
Contributor Author

ionysos commented Jul 10, 2019

@ialidzhikov Thanks for your comment. Unfortunately, this only works for building the sources but not for (unit) testing them. And the problem which results and which is mentioned here is the result from using it with -mod=vendor.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants