ores.controller.service_definition

Table of Contents

Represents a Kubernetes-style Deployment: the desired configuration for a named service, including how many replicas to run, the binary name, restart policy, and whether the service is enabled. This is a bitemporal table so that the full history of configuration changes is preserved for audit.

Flags

Primary key

UUID primary key for the service definition.

Natural keys

service_name

Unique name of the service (e.g. ores.iam.service).

Columns

binary_name

Executable filename (may differ from service_name for multi-instance services).

desired_replicas

Number of replicas to maintain.

restart_policy

Restart policy: always, on-failure, or never.

max_restart_count

Maximum number of automatic restarts before marking the instance failed.

enabled

1 if the service should be started, 0 if it should remain stopped.

args_template

Optional command-line argument template; NULL means use the default launch arguments.

SQL

Flags

C++

Flags

Repository

Domain includes

#include <string>

Conventions

Qt

Columns (Qt model)

enum_name field header type width
ServiceName service_name Service string 200
BinaryName binary_name Binary string 180
DesiredReplicas desired_replicas Replicas int 70
RestartPolicy restart_policy Restart Policy string 100
MaxRestartCount max_restart_count Max Restarts int 90
Enabled enabled Enabled int 60
Version version Version int 60
ModifiedBy modified_by Modified By string 120

Custom repository methods

See also

Emacs 29.1 (Org mode 9.6.6)