init.yaml file

The init.yaml file (also known as the init description) is used by the einit tool when the einit initializing entity is created.

The init description has the following syntax:

1. The init description begins with the mandatory reserved word entities, followed by a colon. Further, it must list all entities that need to be started after the operating system is loaded.
2. The description of each entity begins with the following string:

   - name: <entity name>

3. If an entity must initiate requests to other entities, i.e. is a client of other entities, its connections must be listed. This list contains the names of server entities to which this entity can send requests, and the name of each connection. The list of connections begins with the reserved word connections, followed by a colon. Each element of the list of connections is described in the following format:

   - target: <server entity name>

   id: <connection name>

If an entity does not have connections with other entities or acts as the server in all of its connections, its list of connections should be left blank.

Below is an example of an init description file for a simple solution containing two entities (client and server). Please note this again: a connection is described only once, specifically in the client entity section.

init.yaml

entities:

# The client entity can send requests to the server entity.

- name: client

connections:

# Name of the entity to which the client entity can send requests

- target: server

# Name of the connection used for IPC messaging between entities

id: server_connection

# The server entity operates in the server role (responds to requests).

- name: server

You are not required to create static description files for the einit entity. These files are included in the KasperskyOS Starter Kit toolkit and are automatically connected during a solution build. However, the einit entity should be described in the security.cfg file.

Page top