... | ... | @@ -29,6 +29,8 @@ Related requirement: https://gitlab.isc.org/isc-projects/stork/-/issues/43 |
|
|
|
|
|
Configuration tracking may sound a bit complicated, but Stork already stores the current configuration in the database as JSONB. We also have a mechanism to detect configuration changes. A new table needs to be added to store old configurations with appropriate metadata and a trigger in the database to move the current configuration to this new table.
|
|
|
|
|
|
### 2.1 Phase 1: Visualising Kea configuration
|
|
|
|
|
|
Here's a high level sketch of tasks required to complete phase 1:
|
|
|
|
|
|
- Evaluate if stork-server code (written in go) provides an API to make the configuration available. The Kea config information is there and there are API calls (such as `/hosts`, `/overview`, `/shared-networks` and `/subnets`) that return specific fragments of the configuration, but most likely there will be a need to implement new API call that returns it as a whole JSON structure.
|
... | ... | |