meta_data.json description

The meta_data.json file contains information about the current packet and provides the ability to send output of db_converter to messenger. The current implementation supports only mattermost integration.

General structure of meta_data.json:

{
    "type": < "default" | "read_only" | "no_commit" | "maintenance" | "export_data" >,
    "client_min_messages": < "DEBUG1" | "LOG" | "NOTICE" | "WARNING" | "ERROR" >,
    "hook": {
        "type": < "matterhook" | "slack" >,
        "username": text,
        "verbosity": [ "resultset" | "stm_result" | "raise" | "all" ],
        "channel": text,
        "message": text
    },
    "postgresql": {
        "statement_timeout": "180s"
    }
}

Packet types

Possible values of type field:

Value	Action tracker	Description
default	Yes	If the type field is not initialized or has the value default, then the package is tracked in the target database during deployment. The entire content of meta_data.json will be written to dbc_packets.meta_data
read_only	No	The transaction will be opened in SET TRANSACTION READ ONLY mode. This mode can be used to implement notifications when the DB state does not change. When launching packet of this type, the execution result is not recorded in the target database, i.e. the packet can be launched an unlimited number of times. Read only packet example.
no_commit	No
maintenance	No
export_data	No

client_min_messages

Hooks