| commit | b2cac08ef541db9969425fe5ef1c04660679e180 | [log] [tgz] |
|---|---|---|
| author | Mateusz Zalega <mateusz@monogon.tech> | Thu Jul 14 14:55:43 2022 +0200 |
| committer | Mateusz Zalega <mateusz@monogon.tech> | Thu Aug 11 11:32:14 2022 +0000 |
| tree | 6331eebaeba6b8f728234f07957bb25cc381290d | |
| parent | 073a1c562f386ac9b33d5361a380098e5d3fdd74 [diff] |
m/c/metroctl: log resolver state This makes metroctl log the resolver's output, given the --verbose flag is provided. Change-Id: If4578341b733b7ba0ae86bc31dac2f841e75e1ad Reviewed-on: https://review.monogon.dev/c/monogon/+/836 Tested-by: Jenkins CI Reviewed-by: Sergiusz Bazanski <serge@monogon.tech>
This is the main repository containing the source code for the Monogon Project.
This is pre-release software - feel free to look around, and check back later for our first release!
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 -c dbg
Run a kubectl command:
scripts/bin/bazel run //metropolis/cli/dbg -c dbg -- kubectl describe
Run tests:
scripts/bin/bazel test -c dbg //...