commit | 50009e024b50eda2c69b884600d0850c73d62b6d | [log] [tgz] |
---|---|---|
author | Serge Bazanski <serge@nexantic.com> | Wed Jul 07 14:35:27 2021 +0200 |
committer | Sergiusz Bazanski <serge@nexantic.com> | Wed Jul 07 13:48:54 2021 +0000 |
tree | 28ee724fd39c537e09a755fbd593dc15d31e288e | |
parent | ebe025936fc86f53e7316f894f54dd6ef9b0a9d7 [diff] |
m/n/core/consensus: parse etcd server logs This finally gives us easy to read etcd logs instead of raw JSON dumps into stdout. Instead of simply parsing them as raw logs, we convert them into leveled logs. Change-Id: I7cfe18b9c4e24d7742a01a77f5d9c6ddee647493 Reviewed-on: https://review.monogon.dev/c/monogon/+/209 Reviewed-by: Leopold Schabel <leo@nexantic.com>
This is the main repository containing the source code for the Monogon Project.
⚠️ This is pre-release software that happens to be publicly available. Nothing to see here, please move along.
Our build environment requires a working Podman binary (your distribution should have one).
Spinning up: scripts/create_container.sh
Spinning down: scripts/destroy_container.sh
Running commands: scripts/run_in_container.sh <...>
Using bazel using a wrapper script: scripts/bin/bazel <...>
(add to your local $PATH for convenience)
This repository is compatible with the IntelliJ Bazel plugin, which enables full autocompletion for external dependencies and generated code. All commands run inside the container, and necessary paths are mapped into the container.
The following steps are necessary:
Install Google's Bazel plugin in IntelliJ. On IntelliJ 2020.3 or later, you need to install a beta release of the plugin.
Add the absolute path to your ~/.cache/bazel-monogon
folder to your idea64.vmoptions
(Help → Edit Custom VM Options) and restart IntelliJ:
-Dbazel.bep.path=/home/leopold/.cache/bazel-monogon
Set "Bazel Binary Location" in Other Settings → Bazel Settings to the absolute path of scripts/bin/bazel
. This is a wrapper that will execute Bazel inside the container.
Use File → Import Bazel project... to create a new project from .bazelproject
.
After running the first sync, everything should now resolve in the IDE, including generated code.
Launch the node:
scripts/bin/bazel run //:launch
Run a kubectl command:
scripts/bin/bazel run //metropolis/cli/dbg -- kubectl describe
Run tests:
scripts/bin/bazel test //...