mirror of
https://github.com/zeek/zeek.git
synced 2025-10-16 05:28:20 +00:00
77556e9f11
This separates uploading a configuration from deploying it to the instances into separate event transactions. set_configuration_request/response remains, but now only conducts validation and storage of the new configuration (upon validation success, and not yet persisted to disk). The response event indicates success or the list of validation errors. Successful upload now returns the configuration's ID in the result record's data struct. The new deploy_request/response event takes a previously uploaded configuration and deploys it to the agents. The controller now tracks uploaded and deployed configurations separately. Uploading assigns g_config_staged; deployment assigns g_config_deployed. Deployment does not affect g_config_staged. The get_config_request/response event pair now allows selecting the configuration the caller would like to retrieve. |
||
|---|---|---|
| .. | ||
| agent | ||
| controller | ||
| node | ||
| supervisor | ||
| __load__.zeek | ||
| config.zeek | ||
| log.zeek | ||
| persistence.zeek | ||
| request.zeek | ||
| types.zeek | ||
| util.zeek | ||