| commit | 8d45a0598ae83b8da89442ce8960e64f065182c7 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@monogon.tech> | Mon Oct 18 17:24:24 2021 +0200 |
| committer | Sergiusz Bazanski <serge@monogon.tech> | Wed Nov 03 15:01:37 2021 +0000 |
| tree | 76fc262f260152be7be130ed2a078738e03073c2 | |
| parent | 52304a8aa84604846e316e28c955b67e68c52f34 [diff] |
m/pkg/event/etcd: implement ranged watchers This adds a new mode of operation to etcd Values/Watchers in which a range of etcd keys is watched for updates instead of a single key. This allows the implementation of watching a collection of objects stored in etcd for updates, eg. the node state in the Curator. This has been implemented within the existing API of Event Values, which is likely the biggest contention point of this change. An alternative would be to design a separate API for multi-value use, but this should allow us to more easily integrate with the existing code. We make use of Go's options-as-varargs paradigm to not break any existing use of this codebase. Some behaviour of the Get() operation in ranged context is left underdefined, but none of the expected users of this codebase are expected to depend on this. Once the dust settles a bit, we can attempt to formalize this more strongly. Change-Id: I8f84d74332765e52b9bbec04b626d00f05c23071 Reviewed-on: https://review.monogon.dev/c/monogon/+/419 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
Run a kubectl command:
scripts/bin/bazel run //metropolis/cli/dbg -- kubectl describe
Run tests:
scripts/bin/bazel test //...