*: fix gomodproxy compatibility

This is necessary for the source to be fetchable from third-party Go
projects (currently via a replace directive, as source.monogon.dev isn't
go-getable). Otherwise, `go mod tidy` complains:

reading https://sum.golang.org/lookup/github.com/monogon-dev/monogon@v0.0.0-20230223122556-665b10937eb8: 404 Not Found
	server response:
	not found: create zip: build/analysis/BUILD.bazel: case-insensitive file name collision: "BUILD" and "build"
	build/analysis/importsort/BUILD.bazel: case-insensitive file name collision: "BUILD" and "build"
	build/analysis/importsort/classify.go: case-insensitive file name collision: "BUILD" and "build"
	build/analysis/importsort/importsort.go: case-insensitive file name collision: "BUILD" and "build"
	build/analysis/importsort/importsort_test.go: case-insensitive file name collision: "BUILD" and "build"
	build/analysis/importsort/testdata/README.md: case-insensitive file name collision: "BUILD" and "build"
	[Truncated: too long.]

Change-Id: If5947be74f7dfcf4ba4bd79c4dc37589f324b891
Reviewed-on: https://review.monogon.dev/c/monogon/+/1223
Tested-by: Leopold Schabel <leo@monogon.tech>
Reviewed-by: Leopold Schabel <leo@monogon.tech>
40 files changed
tree: 6093a955f5c08f29e6590fb71781849d100a3e0e
  1. .github/
  2. build/
  3. cloud/
  4. go/
  5. intellij/
  6. metropolis/
  7. third_party/
  8. tools/
  9. .bazelignore
  10. .bazelproject
  11. .bazelrc
  12. .bazelrc.sandboxroot
  13. .bazelversion
  14. .git-ignore-revs
  15. .gitignore
  16. BUILD.bazel
  17. CODING_STANDARDS.md
  18. go.mod
  19. go.sum
  20. LICENSE
  21. README.md
  22. SETUP.md
  23. WORKSPACE
README.md

Monogon Monorepo

This is the main repository containing the source code for the Monogon Platform.

This is pre-release software - take a look, and check back later!

Environment

Our build environment is self-contained and requires only minimal host dependencies:

  • A Linux machine or VM.
  • Bazelisk >= v1.15.0
  • A reasonably recent kernel with user namespaces enabled.
  • Working KVM with access to /dev/kvm (if you want to run tests).

Our docs assume that Bazelisk is available as bazel on your PATH.

Refer to SETUP.md for detailed instructions.

Monogon OS

Run a single node demo cluster

Build CLI and node image:

bazel build //metropolis/cli/dbg //:launch -c dbg

Launch an ephemeral test node:

bazel test //:launch -c dbg --test_output=streamed

Run a kubectl command while the test is running:

bazel-bin/metropolis/cli/dbg/dbg_/dbg kubectl describe node

Test suite

Run full test suite:

bazel test -c dbg //...