KV Management

Set the KV container name

Changed on

Several Temps instances sharing one Docker daemon each need their own KV container. The default is already unique per instance; set a name here to choose it yourself. Must start with redis-; an empty value restores the default. Refused with 409 while the KV service exists: renaming its container would orphan the data, so delete the service first.

patch/kv/settings

Request

  • Base URL: /api (relative, and the document was published on a file host, not at the API’s origin)
  • URL: /api/kv/settings
  • Auth: HTTP bearer

Request body

container_namestring required

New container name. Empty resets to the per-instance default. Must start with the service's prefix (redis- for KV, rustfs- for Blob).

Example request

{
  "container_name": "redis-temps-kv-staging"
}

Response

Container name saved

container_namestring required

Docker container the service runs in on this instance.

customboolean required

Whether an operator-chosen name is saved.

default_container_namestring required

The container an empty setting resolves to: the pre-existing fixed name when this install already enabled the service, otherwise a name derived from this instance.

in_useboolean required

Whether the service already exists. The name cannot change then: delete the service first.

required_prefixstring required

Every container name for this service must start with this.

Example response

{
  "container_name": "redis-temps-kv-3fa91c07",
  "default_container_name": "redis-temps-kv-3fa91c07",
  "required_prefix": "redis-"
}

Changes