drc-vantage 2.0

Thin HTTP client for the Vantage platform. Talks only to the Next.js API (VANTAGE_API_URL) with a developer account API key.

Install

pip install drc-vantage
# or
uv add drc-vantage

Configuration

Quick start (Client-centric)

from vantage import Client

client = Client()

# KPI: create → chain governance on the same handle
my_kpi = client.kpis.create(
    name="Monthly revenue",
    dataset_id="…",
    definition_type="MANUAL",
    manual_config={"valueField": "amount", "aggregation": "SUM"},
)
my_kpi.assign_to_team("analytics")
my_kpi.assign_owner("owner@example.com")

# Lookup
record = client.kpis.find_by_name("Monthly revenue")
existing = client.kpis.for_id(record.id)

# Dataset
dataset = client.datasets.register(
    location={"schema": "marts", "table": "nps"},
    name="NPS",
    type="TABLE",
    storage_system_slug="postgresql",
)
dataset.assign_to_team("customer-success")
dataset.analyze_and_check_alerts()

# Ingestion
client.ingestion.storage_systems.register(
    slug="wh-pg",
    env_key="DRC_PG",
    name="Warehouse PostgreSQL",
    kind="POSTGRESQL",
    config={"database": "analytics"},
)

# Platform admin
client.platform.teams.create(name="Analytics")

Public exports

Client, catalogue exceptions (NotFoundError, AmbiguousLookupError), Page, and orchestration helpers (vantage_flow, orchestration_hooks, …).

This package ships a py.typed marker — use Pylance/Pyright basic type checking or stricter for full namespace and create/register parameter hints.

Resource types and records: from vantage.resources import KpiResource or from vantage.catalogue import KpiRecord.

Migration from 1.x

Orchestration

See previous examples using vantage_flow, orchestration_hooks, and client.ingestion.data_sources.register inside Prefect flows.