| commit | b1e7ee4984d057ca1aeacd8e0d1489aa700cdf0c | [log] [tgz] |
|---|---|---|
| author | Mateusz Zalega <mateusz@monogon.tech> | Fri Jul 08 12:19:02 2022 +0200 |
| committer | Mateusz Zalega <mateusz@monogon.tech> | Mon Jul 11 12:09:15 2022 +0000 |
| tree | 6e0780e12d525cbf6393771af8100204e9668110 | |
| parent | f1234a9528f700bc3c44a45fe19d5a743da29af5 [diff] |
m/c/metroctl: use the global endpoints parameter This makes the takeownership command use the global --endpoints parameter instead of its positional argument. Change-Id: I1ddb27fb1cbb5b299c97b6c0bca26883c9a51329 Reviewed-on: https://review.monogon.dev/c/monogon/+/829 Tested-by: Jenkins CI Reviewed-by: Lorenz Brun <lorenz@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 //...