Skip to main content

vibedata-dlt-studio-secrets

Shared Secret Store registration for the Studio execution units of the VibeData dlt runtime. A dependency package, not a runnable distribution.

A Domain binds one Secret Store — local_toml, azure_key_vault, studio_key_vault, or motherduck_flight_secrets — independently of its Data Platform (ADR-0022). dlt reads a local_toml store natively from the mounted secrets.toml; every other kind needs a dlt config provider registered in the same interpreter before the first dlt.secrets read. Every Studio unit (Fabric Lakehouse, Fabric Warehouse, DuckDB/MotherDuck) performs that registration through this package, so the behaviour is identical whichever destination the pipeline targets.

from vibedata.dlt.studio_secrets import register_secret_provider

register_secret_provider()   # reads VD_DOMAIN_SECRET_STORE_KIND; registers what that kind needs
  • register_secret_provider() — the kind-gated entry point every unit's setup_environment() calls first. Raises ValueError when the kind is absent or unknown; registers nothing for local_toml. For motherduck_flight_secrets it registers the Flight secrets provider, whose store is a Flight's injected environment: in this container that resolves nothing, so a credential a container run needs fails where dlt names the field rather than here.
  • register_akv_provider(vault_url=None) — the bare Azure registration, for a process with no destination to configure (source-connection verification). Idempotent: a second call in the same interpreter is a no-op.
  • AzureKeyVaultProvider — the dlt provider. Authenticates through Studio's credential broker on the runtime-declared identity lane and maps the dlt key to a vault secret name. A vault answer of 401 or 403 raises KeyVaultAccessDeniedError naming the vault and the secret, so an access problem is never reported as a missing secret.
  • register_studio_key_vault_provider(vault_url=None) — registers the Internal Studio Key Vault provider. It reads the IAT from the private credential file for each request and calls Studio's AKV-compatible api-version=7.4 Get Secret endpoint directly; it does not invoke the credential broker.

Metadata

Release files for vibedata-dlt-studio-secrets 0.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for vibedata-dlt-studio-secrets 0.4.0
File Size Uploaded Provenance
vibedata_dlt_studio_secrets-0.4.0.tar.gz 12.0 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for vibedata-dlt-studio-secrets 0.4.0
File Interpreter ABI Platform
vibedata_dlt_studio_secrets-0.4.0-py3-none-any.whl Python 3 none any Details

Total release size: 19.7 kB

Release files / vibedata_dlt_studio_secrets-0.4.0.tar.gz

Download URL vibedata_dlt_studio_secrets-0.4.0.tar.gz
Size 12.0 kB
Tags Source
SHA-256 checksum
How to use checksums
facd9807f15a7a334415b9552fffa922d8b5f792b4f4a02e15c23e3bb848e558
BLAKE2b-256 checksum
How to use checksums
08171a29fa86acf9476f8279a897a70035d128f263b3f21f798fc517387b87fd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.17

Release files / vibedata_dlt_studio_secrets-0.4.0-py3-none-any.whl

Download URL vibedata_dlt_studio_secrets-0.4.0-py3-none-any.whl
Size 7.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4dfd5d42a276e49acfd4397886e4ec85341744b117005f425a0eed24841879fa
BLAKE2b-256 checksum
How to use checksums
3084b421aae0714f7812939e358afe60a594abfa1bb50d04a1403e42056ff641
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.17

Security for vibedata-dlt-studio-secrets 0.4.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page