akili registry
Query and manage the product registry. The registry tracks all data products, their versions, dependency relationships, event contracts, and connectors. Use these commands to understand the dependency graph, analyze change impact, and manage contracts.
Commands
Section titled “Commands”akili registry search
Section titled “akili registry search”Search for products in the registry.
Flags:
| Flag | Short | Default | Description |
|---|---|---|---|
--query | -q | Search query string |
Examples:
# Search for products matching "orders"akili registry search -q orders
# List all registry entries (no filter)akili registry search
# As JSONakili registry search -q orders --jsonakili registry get <id>
Section titled “akili registry get <id>”Get the registry entry for a specific product.
Arguments:
| Argument | Type | Required | Description |
|---|---|---|---|
id | string | yes | Product ID |
Examples:
# Get registry entryakili registry get daily-ordersakili registry contract <id>
Section titled “akili registry contract <id>”Show the dependency contract for a product, including its upstream dependencies and downstream dependents.
Arguments:
| Argument | Type | Required | Description |
|---|---|---|---|
id | string | yes | Product ID |
Examples:
# View dependency contractakili registry contract daily-orders
# As JSONakili registry contract daily-orders --jsonakili registry graph
Section titled “akili registry graph”Show the full dependency graph of all products in the registry.
Examples:
# View full dependency graphakili registry graph
# As JSON for visualization toolsakili registry graph --jsonakili registry impact <id>
Section titled “akili registry impact <id>”Analyze the impact of changing a specific product. Shows all downstream products that would be affected.
Arguments:
| Argument | Type | Required | Description |
|---|---|---|---|
id | string | yes | Product ID |
Examples:
# Analyze impact of changing a productakili registry impact daily-orders
# As JSONakili registry impact daily-orders --jsonakili registry validate-deps <id>
Section titled “akili registry validate-deps <id>”Validate that all dependencies for a product are resolvable and healthy.
Arguments:
| Argument | Type | Required | Description |
|---|---|---|---|
id | string | yes | Product ID |
Examples:
# Validate dependenciesakili registry validate-deps daily-ordersakili registry connectors
Section titled “akili registry connectors”List all connectors available in the registry.
Examples:
# List connectorsakili registry connectors
# As JSONakili registry connectors --jsonakili registry register-contract
Section titled “akili registry register-contract”Register an event contract for a product.
Flags:
| Flag | Short | Default | Description |
|---|---|---|---|
--product-id | Product ID (required) | ||
--version | Contract version (required) |
Examples:
# Register a contractakili registry register-contract --product-id daily-orders --version v1.0.0akili registry contracts <product_id>
Section titled “akili registry contracts <product_id>”List all event contracts for a specific product.
Arguments:
| Argument | Type | Required | Description |
|---|---|---|---|
product_id | string | yes | Product ID |
Examples:
# List contracts for a productakili registry contracts daily-ordersakili registry subscribers <topic>
Section titled “akili registry subscribers <topic>”Find all subscribers for a given event topic.
Arguments:
| Argument | Type | Required | Description |
|---|---|---|---|
topic | string | yes | Topic name |
Examples:
# Find subscribers for a topicakili registry subscribers orders.createdakili registry detect-cycles
Section titled “akili registry detect-cycles”Detect dependency cycles in the product registry graph.
Examples:
# Check for cyclesakili registry detect-cycles# No dependency cycles detected
# Or if cycles exist:# Dependency cycles detected!