Migrate to Go modules#367
Conversation
|
What's the thinking behind re-adding the vendor directory? From what I read this is only for compatibility with non-module-aware versions of Go? |
The idea is that CI doesn't have to download all the module files. |
|
OK, that sounds reasonable. |
|
/test-centos-integration |
|
/test-centos-integration |
1 similar comment
|
/test-centos-integration |
|
/lgtm |
|
New changes are detected. LGTM label has been removed. |
|
Updated to use operator-sdk
|
|
More context: The current Prow job uses Go 1.12; this version doesn't automatically detect go modules. The next version, 1.13 does. All jobs which use the We are migrating to use go modules because the operator-sdk forces us to. |
Surely that's just a matter of setting the environment variable |
Yes. But 1.13.x is the latest stable? |
|
It seems that the canned jobs don't use our |
|
/retest |
1 similar comment
|
/retest |
|
/test-integration |
|
/test-integration |
This was recently changed, and this seems to be a left behind by accident.
|
/test-integration |
|
/test gofmt |
|
/test-integration |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: honza, stbenjam The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
This looks good. |
I am a git wizard 😎 I can move some commits around. I tried to make everything explicit in #444
The commit messages in the new PR are much more explicit about what's going on. |
|
Closing in favor of #444 |
OCPBUGS-36425: Sync jul 30
Steps taken:
dep ensureto make sure that the vendor directory is up-to-datego mod init ...to create Go module filesoperator-sdkcli tool to the latest versiongo.moddeptool from MakefileOfficial migrating to Go modules documentation