| commit | efdb6e9da9ed4d575afe72fde02a27817eca37c4 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Mon Jul 13 17:19:27 2020 +0200 |
| committer | Serge Bazanski <serge@nexantic.com> | Mon Jul 13 17:19:27 2020 +0200 |
| tree | b1e1a9bff4b1b91ada8da8673e042bfecda2f505 | |
| parent | b7689bd2d426a5b5fa8375bb6e72aa853610707f [diff] |
core/api: move to core/proto This is keeping in line with conventions that protobuf files generally live in a 'proto/' directory. Even without that, a lot of the protos in there aren't actually part of an API, so keeping them in `api/` is a bit of a misnomer. We also remove unused protos that were part of the old integrity/lifecycle flow. Again, these will make a comeback. Test Plan: this should fail. part of a larger stack. D590 is the first tip of the stack that should work. X-Origin-Diff: phab/D588 GitOrigin-RevId: 4a7af494810348f6bcabd49e63902b4c47e6ec35
This is the monorepo storing all of nexantic's internal projects and libraries.
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)
Launch the node:
bazel run //:launch
Run a kubectl command:
bazel run //core/cmd/dbg -- kubectl describe
This repository is compatible with the IntelliJ Bazel plugin. All commands run inside the container, and necessary paths are mapped into the container.
We check the entire .ijwb project directory into the repository, which requires everyone to use the latest version of both IntelliJ and the Bazel plugin, but eliminates manual setup steps.
The following steps are necessary:
Install Google's official 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.
Open the .ijwb folder as IntelliJ project.
Disable Vgo support for the project.
Run a non-incremental sync in IntelliJ
The plugin will automatically resolve paths for generated files.
If you do not use IntelliJ, you need to use the scripts/bazel_copy_generated_for_ide.sh script to copy files locally.