Overview

Entity field parameters

Type

Possible value types:

Type Description Examples — Empty value

uuid

Identifier

"00000000-0000-0000-0000-000000000000

str

String

"Value" — ""

int

Integer

125 — 0

float

Float

2.83 — 0.0

date

Date in RFC3339

"2019-09-06T09:12:00Z"

object

JSON object

{"key":"abcdef", "order":125} — {}

array<str>

JSON array of str types

["abc", "def", "xxx"] — []

array<int>

JSON array of int types

[5, 10, -3] — []

array<object>

JSON array of object types

[{"k":"abc"}, {"k":"def"}] — []

array<T>

JSON array of <T> types

[<T>, <T>] — []

json

JSON value (object, array, quoted string, number, null)

"\"abc\"", {"a":123}"  — {}

any

Any value

"abc", {"a":123} — ""

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).