data.registry.account.persist

Create a RegistryAccount row (DB only, UUID-only public surface)

Create a registry account row in the LtInteg DB (no provider calls).

Overview

Property	Value
Workflow type	Atomic
Library	App-registry
Version	1.0

Input Schema

Field	Type	Required	Default	Description
organization_uuid	uuid	Yes	—	UUID of the organization that will own the registry account
cloud_connection_uuid	uuid	Yes	—	UUID of the CloudConnection backing this registry account
name	string	Yes	—	Human-readable name (unique per organization among live rows)
backend_type	string	Yes	—	Registry backend (ecr, gcr, github_ghcr, ...) — RegistryBackendType value
description	string	No	—	Optional free-text description
region	string	No	—	Provider region (e.g. us-east-1)
namespace	string	No	—	Provider namespace / org / project segment
project_or_account_ref	string	No	—	Provider project/account reference (e.g. AWS account, GCP project)
config	dict	No	—	Backend-specific configuration blob
provider_metadata	dict	No	—	Provider-supplied metadata (read-only mirror)
actor_uuid	uuid	No	—	UUID of the user creating the account (recorded as created_by)

Output Schema

Field	Type	Required	Default	Description
registry_account_uuid	uuid	Yes	—	UUID of the RegistryAccount that was created
created_at	string	Yes	—	ISO-8601 timestamp of the creation
organization_uuid	uuid	No	—	Organization UUID echoed from input
cloud_connection_uuid	uuid	No	—	Cloud connection UUID echoed from input
name	string	No	—	Name echoed from input
failure_reason	string	No	—	Human-readable failure reason
failure_type	string	No	—	Engine failure type classification (ADR-015 E2)
failed_action	string	No	—	Action name that caused the failure (ADR-015 E2)
failed_at_state	string	No	—	State name where the failure occurred
failed_step	string	No	—	Failed DAG step name when reported by the engine
failed_layer	integer	No	—	1-based failed DAG layer number emitted by the engine
error	string	No	—	Unexpected error message
error_type	string	No	—	Unexpected error class or type

States

State	Initial	Terminal	Success	Auto-advance	Description
pending	Yes	No	—	complete	Persist registry account
completed	No	Yes	Yes	—	Persisted
failed	No	Yes	No	—	Persist failed

State Diagram

Transitions

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

API Usage

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

{
  "workflow_type": "data.registry.account.persist",
  "initial_data": {
    "organization_uuid": "value",
    "cloud_connection_uuid": "value",
    "name": "value",
    "backend_type": "value"
  }
}