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
..
files	Remove trailing whitespace from script files	2021-10-20 09:57:09 -07:00
frameworks	Management framework: introduce state machine for configs and persist them	2022-06-21 17:22:45 -07:00
integration	Remove trailing whitespace from script files	2021-10-20 09:57:09 -07:00
misc	Remove trailing whitespace from script files	2021-10-20 09:57:09 -07:00
protocols	Include certificate information in SSL::Weak_Key notice	2022-05-11 18:56:04 +01:00
tuning	Remove trailing whitespace from script files	2021-10-20 09:57:09 -07:00