Christian Kreibich 46db4a0e71 Management framework: introduce state machine for configs and persist them ... 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.		2022-06-21 17:22:45 -07:00
..
control	Remove trailing whitespace from script files	2021-10-20 09:57:09 -07:00
dpd	Add analyzer_confirmation and analyzer_violation events	2021-11-23 19:36:50 -07:00
files	update uses of "when" in base scripts to include captures	2022-01-07 14:53:33 -08:00
intel	Fix host header normalization in intel framework.	2021-12-21 21:54:47 +01:00
management	Management framework: introduce state machine for configs and persist them	2022-06-21 17:22:45 -07:00
netcontrol	Support for log filter policy hooks	2020-09-30 12:32:45 -07:00
notice	update uses of "when" in base scripts to include captures	2022-01-07 14:53:33 -08:00
packet-filter	More bro-to-zeek renaming in scripts and other files	2019-05-16 02:36:41 -05:00
signatures	Hopefully the last major script reorganization.	2011-08-05 23:09:53 -04:00
software	update uses of "when" in base scripts to include captures	2022-01-07 14:53:33 -08:00