Migrating to Go Modules

A Recipe for Migrating to Go Modules

Kat Cosgrove ◂ ◂ ◂ ◂ ◂ IoT Engineer Developer Advocate Twitter: Dixie3Flatline Email: KatC@jfrog.com bit.ly/GoPolandJFrog 2

Modules are the Default …and migrating is easier than you think!

Mender.io ◂ Used for large-scale IoT deployments ◂ Build as a collection of microservices ◂ Varying version tags between services @Dixie3Flatline jfrog.com/shownotes @jfrog 4

Get a go.mod file go mod init ◂ ◂ ◂ ◂ ◂ Glide Godeps Govendor Dep … and more! v2+ ◂ ◂ ◂ ◂ Slightly more complex Increment major version Add to module path Causes some other issues to address `go mod init github.com/mendersoftware/deviceauth/v3’ @Dixie3Flatline jfrog.com/shownotes @jfrog 5

Update imports ◂ ◂ ◂ ◂ @Dixie3Flatline Build and test Both will likely fail Update import statements for new path May want to use a script for this in large projects jfrog.com/shownotes @jfrog 6

Module Versioning ◂ After go mod init or go mod tidy, check version numbers ◂ Some dependencies may cause problems here ◂ Untagged changes in satori/go.uuid broke Mender ◂ At this point, you should be able to build and run tests @Dixie3Flatline jfrog.com/shownotes @jfrog 7

Module Proxy ◂ ◂ ◂ ◂ ◂ JFrog GoCenter Immutable and persistent modules Much faster than cloning Consistent, secure, reproducible builds Vulnerability scanning built in export GOPROXY=https://gocenter.io @Dixie3Flatline jfrog.com/shownotes @jfrog 8

Static Analysis and Code Generators ◂ Some projects may need to handle additional issues with paths here ◂ Remember to look at your .proto and Dockerfiles @Dixie3Flatline jfrog.com/shownotes @jfrog 9

Testing Changes ◂ Go v1.13 made changes to testing ◂ Specifically, when flags are parsed ◂ Move flag.Parse() to main test function @Dixie3Flatline jfrog.com/shownotes @jfrog 10

Thanks! Any questions? You can find me at ◂ ◂ ◂ @Dixie3Flatline katc@jfrog.com bit.ly/GoPolandJFrog 11