"Adopting Go Modules in NATS v2: A Song of Ice and Fire"
summary
NATS v2 migrates to Go modules, renames repositories and bumps the module path to a v2 module path and that change breaks go get due to a go1.12/1.13 regression producing a no such file or directory error for repos with dots; mitigations include archiving old repos, limiting v2 tagging to the server, requiring explicit /v2 import paths, and relying on Go fixes plus go proxy/Athens support so module builds finally succeed.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:37About Waldemar
- 1:32About the CNCF
- 2:10About v2
- 2:40Go Modules
- 5:26Documentation
- 5:58Go Client
- 6:35Go Get
- 7:08Go Modules Guide
- 7:38Conclusion
related talks
33mTransition to Go 2
15mMulti-Module Repositories
27mHow to Avoid Breaking Changes in your Go Modules
38mUsing Go Modules in everyday life
07mBuilding A Central Go Modules Repository
06mLightning Talk: Getting The Most Out Of Go Tool Dependencies
33mHow to Safely and Efficiently Build your App with Modules
28mState of the Go Nation!