| commit | 72068da814af80568cb106b877ef8f5e526e684c | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Tue Mar 16 13:15:45 2021 +0100 |
| committer | Serge Bazanski <serge@nexantic.com> | Tue Mar 16 13:15:45 2021 +0100 |
| tree | 31831657903e62d4a813c9d18d47413154f13560 | |
| parent | d8af5bf4c14a5c53d1736695a1210b6eea4d246e [diff] |
metropolis/proto: add private We add a new proto package, 'private'. This will hold all non-public proto messages for the implementation of the cluster lifecyclce design document. We duplicate 'internal' for two reasons: - make it easier to port code accross to use the new protos/cluster code, while slowly phasing out protos/internal. - 'internal' was a poor name choice, as it's significant in Go path naming, and might cause some problems in the future. We have Bazel's visiblility mechanism to protect accidental use. Test Plan: New proto, not yet used - see rest of stack. X-Origin-Diff: phab/D732 GitOrigin-RevId: 15632353c46068b4f4c5025828c9c8459feaa335
This is the main repository containing Monogon's public source code, including Metropolis.
We assume a Fedora host system provisioned using rW, and IntelliJ as the IDE.
For better reproducibility, all builds are executed in containers.
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. 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.
Add the absolute path to your ~/.cache/bazel-nxt folder to your idea64.vmoptions (Help → Edit Custom VM Options) and restart IntelliJ:
-Dbazel.bep.path=/home/leopold/.cache/bazel-nxt
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.
It's strongly recommend to use our project presets for file watchers and other IDE features. Run this command and re-open the project in order to install them:
bazel run intellij/localconfig $(pwd)
Launch the node:
bazel run //:launch
Run a kubectl command:
bazel run //metropolis/cli/dbg -- kubectl describe