SWEAGLE offers a set of APIs that allows creating, managing, and updating the config data set without the need for manual interactions through the user interface. There is a set of endpoints available to support the most common actions in each of the key steps in the life cycle of the configuration data.
The "collect" is the step in which changes to the configuration data are brought into SWEAGLE. This consists of opening a data changeset, adding all the changes on nodes and CDIs into the changeset, validating there are no blocking factors, and approving the data changeset in order to apply the changes to the data model.
The "consolidate" is where the applied changes are evaluated in the data model, listing the config data sets that are impacted by the data changes and for which there is pending data, and run any relevant validators to ensure there are no violations.
The "snapshot" step is where the pending data is stored as an unalterable snapshot for every config data set. The new snapshot automatically becomes the current active snapshot which can be consumed through the API. All snapshots are stored in the system, and the history is available for analysis and comparison such as the DIFF calculation between any 2 snapshots in time.
The "consume" step is where other tools and processes can request snapshot data through the API. Those requests can be for the full "dump" of the snapshot in a particular format, or it can be a request for a particular part of the data by calling a specific "exporter" with arguments.
| collect |
| |
| consolidate |
| |
| snapshot |
| |
| consume |
|
