vd-duckdb-dlt-studio 0.3.0

VD Studio dlt runtime for intent (Studio-local) runs targeting DuckDB — secrets from the operator-managed secrets.toml pinned via VD_LOCAL_SECRETS_DIR

vd-duckdb-dlt-studio

VD Studio dlt runtime for intent (Studio-local) runs targeting DuckDB.

Ships the vd_duckdb_dlt_utils import package (same two-call API convention as the Fabric distributions — exactly one of the family is installed per execution unit, selected at intent creation by the Domain's destination):

import dlt
from vd_duckdb_dlt_utils import setup_environment, finalize

setup_environment()
pipeline = dlt.pipeline(pipeline_name="my_pipeline", destination="duckdb", dataset_name="src_x")
try:
    pipeline.run(source)
except Exception as e:
    finalize(pipeline, error_message=str(e))
    raise
finalize(pipeline)

Secrets resolve from the operator-managed $VD_LOCAL_SECRETS_DIR/secrets.toml (Studio sets the env var per intent), keyed [<connection>.credentials]. The provider rewrites the pipeline segment to the connection name resolved from the pipeline folder's config.toml ([pipeline].connection), so any pipeline name resolves the connection's secrets.