mirror of
https://github.com/zeek/zeek.git
synced 2025-10-08 17:48:21 +00:00
![]() The controller now knows three states that a cluster configuration can be in: - STAGED: as uploaded by the client - READY: with needed tweaks applied, e.g. to fill in ports - DEPLOYED: as sent off to agents for deployment These states aren't exclusive, they represent checkpoints that a config goes through from upload through deployment. A deployed configuration will also exist in its STAGED and READY versions, unless a client has uploaded a new configuration, which will overwrite the STAGED and READY ones. The controller saves all of these in a table, which lets us use Broker to persist all states to disk. We use &broker_allow_complex_type, since we only ever store entire configurations. |
||
---|---|---|
.. | ||
base | ||
policy | ||
site | ||
zeekygen | ||
CMakeLists.txt | ||
test-all-policy.zeek |