kv.key.set

Write one Orkestia KV key as a new version via LTIP (value redacted)

Write one Orkestia KV key's value as a new version through the LTIP SecretContract/KVEntryContract for the bound provider.

Inputs:

• connection_uuid: Bound provider CloudConnection (required)
• app: App slug — KV scope (required)
• environment: Environment scope, e.g. production (required)
• namespace: Namespace (optional, defaults to app)
• key: Logical key, e.g. DATABASE_URL (required)
• tier: plain | secret (required)
• value: Seed value — sensitive; never persisted or logged (required)
• ttl_seconds: Optional TTL

Outputs (reference only — no value):

• provider_resource_id, version_id, key, tier, namespace, provider, created_at

Redaction: value is dropped from state_data at write time and never spread into the output. The {**data} spread is forbidden here. Plugin required: context.get_plugin("<connection provider>")

Overview

Property	Value
Workflow type	Atomic
Library	App-kv
Version	1.0

Input Schema

Field	Type	Required	Default	Description
connection_uuid	uuid	Yes	—	Bound provider CloudConnection.
app	string	Yes	—	App slug (KV scope).
environment	string	Yes	—	Environment scope (dev
namespace	string	No	—	Namespace (defaults to app).
key	string	Yes	—	Logical key, e.g. DATABASE_URL.
tier	string	Yes	—	plain
value	string	Yes	—	Seed value; never persisted or logged.
ttl_seconds	integer	No	—	Optional TTL in seconds.

Output Schema

Field	Type	Required	Default	Description
key	string	No	—	—
tier	string	No	—	—
app	string	No	—	—
environment	string	No	—	—
namespace	string	No	—	—
provider	string	No	—	—
organization_uuid	string	No	—	—
provider_resource_id	string	No	—	ARN/parameter path/secret name (reference, no value).
version_id	string	No	—	—
created_at	string	No	—	—
existed	boolean	No	—	—
connection_uuid	uuid	No	—	—
failure_reason	string	No	—	—
failure_type	string	No	—	—
failed_action	string	No	—	—
failed_at_state	string	No	—	—
failed_step	string	No	—	—
failed_layer	string	No	—	—
error	string	No	—	—
error_type	string	No	—	—

States

State	Initial	Terminal	Success	Auto-advance	Description
pending	Yes	No	—	execute	—
completed	No	Yes	Yes	—	—
failed	No	Yes	No	—	—

State Diagram

Transitions

From	Action	To	Description
pending	execute	completed	—
* (any state)	fail	failed	—

API Usage

POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "kv.key.set",
  "initial_data": {
    "connection_uuid": "value",
    "app": "value",
    "environment": "value",
    "key": "value"
  }
}