Documentation / Resources / Interfaces

Manage Resources with the CLI

List, create, inspect, enable, disable, delete, and assign configured capabilities from reviewed JSON definitions.

Before you begin

Select the namespace and identify the exact Resource kind, id, immutable implementation, configuration, Credential relationship, and Policies. Use a schema-validated JSON file for creation. Platform catalog Resources are visible to tenants but cannot be mutated or deleted by tenant commands.

Steps

  1. List all Resources or filter by kind:
sh
constal resources list --kind service
  1. Create a tenant-managed Resource with constal resources create --body @resource.json.
  2. Inspect its authoritative definition and control head with resources get <kind> <id> and resources control <kind> <id>.
  3. Use resources disable or resources enable with a retained --event-id and optional --reason. Disabling affects new admission; existing Runs retain their accepted snapshot according to runtime rules.
  4. Delete only a tenant-managed Resource after checking consumers and active bindings.
  5. Use the bindings command group for tenant defaults and customer- or principal-scoped assignments. Creation and promotion take reviewed JSON and stable event ids.

Verify

Read the Resource again and confirm the current hash, status, contract, configuration, Policies, and Credential reference. Start a controlled Run, inspect its Resource bindings, and verify the exact accepted CRN rather than relying only on the current revision.

Next steps

Read Use Resources with the SDK, Configure a Resource, Scoped bindings, and the Resources command reference.