commit | 257acab41f5a35575ca0f2dbc9568b1bd75d2570 | [log] [tgz] |
---|---|---|
author | Lorenz Brun <lorenz@monogon.tech> | Tue Aug 10 12:36:17 2021 +0200 |
committer | Lorenz Brun <lorenz@monogon.tech> | Wed Aug 11 11:28:06 2021 +0000 |
tree | fdc41d8de424f74525b7a92024c12f00ed8928fa | |
parent | 1445396219351e711f82d4cebad6e84a46553bda [diff] |
m/p/devicemapper: Support creating read-only devices I originally thought this is not going to be needed as R/W control can be done through devicemapper itself, but verity requires a read-only table. While we're here let's also add some doc comments to the Target struct. Existing functionality is covered by existing tests, read-only functionality will be exercised by verity tests once they land. Change-Id: Ib76bcffb14b5fe40d8d77bd9731b591d0d8cf22f Reviewed-on: https://review.monogon.dev/c/monogon/+/262 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 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 //...