| commit | 9ffa1f9577003ab70a6b483475874f3552d1ccc3 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@monogon.tech> | Wed Sep 01 15:42:23 2021 +0200 |
| committer | Sergiusz Bazanski <serge@monogon.tech> | Thu Sep 02 10:38:15 2021 +0000 |
| tree | a688d02424e8601ed830d12021b5867688d31438 | |
| parent | 6bd415920b84bd695038caeb386f1e97184f0c51 [diff] |
m/n/core/curator: authenticated RPC This adds authentication middleware (server interceptors) for gRPC services running on the public curator listener. Most of this code is testing harnesses to start up just the curator listener with enough of a PKI infrastructure copy from a real Metropolis cluster to be able to start running tests against GetRegisterTicket. Change-Id: I429ff29e3c1233d74e8da619ddb543d56bc051b9 Reviewed-on: https://review.monogon.dev/c/monogon/+/311 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 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 //...