Configure credentials and pipelines
The configuration mechanism in dlt provides a flexible, secure way to define credentials to external systems and other settings separately from your code.
Key features
-
Separation of secrets and configs from code - The main role of the configuration system is to keep sensitive information out of your source code.
-
Built-in credentials -
dltprovides built-in support for most common systems with default/machine credential access. -
Auto-generated configurations - For functions decorated with
@dlt.source,@dlt.resource, and@dlt.destination,dltautomatically generates appropriate configuration specs so they behave like built-in configs and credentials. -
Comprehensive configurability - Nearly all aspects of
dltare configurable, including pipelines, normalizers, loaders, and logging, allowing you to change behavior without modifying code. This capability enables performance optimization and other adjustments at runtime.
📄️ Overview and examples
Learn where configs are stored and how to write them
📄️ Access to configuration in code
Access configuration via dlt function arguments or explicitly
📄️ Vault providers
Learn how to configure Google Secrets and Airflow providers
📄️ Built-in credentials
Configure access to AWS, Azure, Google Cloud and other systems
📄️ How to add credentials
How to add credentials locally and in production