Configuration (configuration)
Description
A structure that unites the infrastructure, logic, and data layers. The entire cluster of the deployed «Incoplax» system is built and operates on the basis of the active configuration.
Initially, the configuration is deployed together with the master server and stored on disk. It contains only one server with a basic set of roles.
Configuration changes are made in the configuration editor application or via the API; after that the configuration is saved in the domain, validated, and, if validation succeeds, can be applied.
Limitations
-
The collection is available only in the master domain.
-
If any field of the configuration object is changed in the DB, after the domain reload the object will not be loaded; a hash check applies.
-
The active configuration cannot be deleted.
-
If there is no active configuration in the master domain, MIC applies the last active configuration from disk.
-
Only one configuration can be in the "active" state.
-
Validation is performed against the current active configuration; thus an arbitrary configuration loaded from outside is in the overwhelming majority of cases invalid.
Fields
{
"id": uuid,
"name": str,
"state": str,
"content": object,
"opts": {
"title": str,
"comment": str
},
"ext": {
"ct": date,
"lwt": date,
"warnings": str,
"errormsg": str,
"activation_time": date,
"deactivation_time": date,
"version": str
}
}
States
| State | Description | Restrictions |
|---|---|---|
|
New configuration |
|
|
Configuration passed validation and is correct; the warning list is in ext.errormsg |
|
|
Configuration is invalid; the error list is in ext.errormsg |
|
|
Start the configuration activation process; as a result the configuration moves to active or error |
|
|
Current active configuration |
|