Consider using a single go.mod for the monorepo

[miguelvr]

Usually Go monorepos use a single go.mod. This makes it easier to develop and to share dependencies.

Replace directives are a massive headache and usually do not play well with IDEs.

Currently there's a multitude of small services or packages that have their own go module, and it's a pain just to start development on an IDE.

[lalitadithya]

Thank you for reaching out!

@miguelvr , would using go workspaces help?

Also, @dims , @mchmarny , what are your thoughts?

[dims]

@lalitadithya YES! we kinda use it already under the covers. see dependencies-update. at the time i was adding that target, i did not want to impose on the team so kept the footprint limited.

BUT yes, i fully support having a go.work/sum in the root directory and updating our workflow/scripts to use it.

[miguelvr]

I'm trying to setup go workspaces, but it's still a major pain

There's more advantages in having a single shared go.mod:

1. easier dependency management - single place to fix CVEs
2. no replace directives
3. better IDE integration

when I first looked at the source code, it felt like packages were being managed in the Rust way, not the Go way, if that makes sense