Config & Discovery

Two kis command groups are clients of the infinity-config service (config.svc): kis config reads and writes runtime configuration, and kis sd inspects the service-discovery subsystem. Both are reachable through the kis launcher.

kis config

What it is. A client to read, write, and watch hive configuration. A hive is a named configuration namespace; within a hive you address values by path.

Why it exists. Platform services need shared configuration that can change at runtime; kis config reads, writes, and watches it from the command line, and can show the hive’s CUE schema and where each value resolves from.

When to reach for it. Inspecting or changing platform/service configuration, or tailing config changes while debugging.

kis config hives                      # list hives + registry version
kis config get <hive> <path>          # read the resolved value
kis config tree <hive> <path>         # list the subtree under a path
kis config set <hive> <path>          # replace the value (PUT)
kis config patch <hive> <path>        # merge a partial document (PATCH)
kis config delete <hive> <path>       # delete the value at a path
kis config schema <hive>              # print the hive's embedded CUE schema
kis config explain <hive> <path>      # full snapshot envelope (where each value resolves from)
kis config watch                      # tail the SSE stream of config changes

Subcommand	Description
`hives`	List hives + registry version exposed by the server
`get`	Read the resolved value at (hive, path)
`tree`	List the subtree under (hive, path)
`set`	Replace the value at (hive, path) via PUT
`patch`	Merge a partial document into (hive, path) via PATCH
`delete`	Delete the value at (hive, path)
`schema`	Print the embedded CUE schema for a hive
`explain`	Fetch the full snapshot envelope and print, for each value, where it resolves from
`watch`	Tail the SSE stream of config changes

kis sd

What it is. A client to the infinity-config service-discovery subsystem. Service instances register and hold a renewable lease; kis sd lists and manages those registrations.

Why it exists. In a multi-service platform, components must discover each other and know which instances are currently alive; service discovery is that registry.

When to reach for it. Inspecting cluster membership, debugging why one service can’t find another, or registering a test instance.

kis sd services                       # list service names with registrations
kis sd instances <service>            # list current instances of a service
kis sd register <service>             # register an instance (mainly for testing)
kis sd heartbeat <lease>              # renew a lease
kis sd deregister <lease>             # revoke a lease
kis sd watch                          # tail the SSE membership stream

Subcommand	Description
`services`	List service names with current registrations
`instances`	List current instances of `<service>`
`register`	Register a service instance (mainly for testing)
`heartbeat`	Renew a lease
`deregister`	Revoke a lease
`watch`	Tail the SSE membership stream