Overview
Entity field parameters
- Type
-
Possible value types:
| Type | Description | Examples — Empty value |
|---|---|---|
|
Identifier |
|
|
String |
|
|
Integer |
|
|
Float |
|
|
Date in RFC3339 |
|
|
JSON object |
|
|
JSON array of str types |
|
|
JSON array of int types |
|
|
JSON array of object types |
|
|
JSON array of <T> types |
|
|
JSON value (object, array, quoted string, number, null) |
|
|
Any value |
|
- Default
-
Default values:
-
required– the field is required when creating a resource. -
generated– generated by the system when creating a resource; in some cases it can be specified at creation, in which case the specified value is used. -
empty– the empty value of the corresponding type. -
str_empty– an empty string.
-
Sections
Categories
The configuration structure is the value of the "content" field of the configuration entity.
Configuration categories are the root elements of the configuration structure.
The configuration can be created directly as a JSON structure or by using the "Configuration Wizard" tool.
The articles below describe the categories and provide examples of their values in JSON structure.
Startup parameters of the server central node are stored separately, on each server disk: Server local configuration (local.cfg.json).
Logical roles (A-Z)
A logical role is a service that implements some isolated system functionality. A role instance runs as an application in one of the nodes on one of the servers and has a unique name across the entire system. The role name starts with a lowercase Latin letter and can consist of Latin letters and digits.