dltaf 0.1.0__tar.gz

dltaf-0.1.0/LICENSE

@@ -0,0 +1,159 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction, and
+distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by the copyright
+owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all other entities
+that control, are controlled by, or are under common control with that entity.
+For the purposes of this definition, "control" means (i) the power, direct or
+indirect, to cause the direction or management of such entity, whether by
+contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the
+outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity exercising
+permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications, including
+but not limited to software source code, documentation source, and configuration
+files.
+
+"Object" form shall mean any form resulting from mechanical transformation or
+translation of a Source form, including but not limited to compiled object code,
+generated documentation, and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or Object form, made
+available under the License, as indicated by a copyright notice that is included
+in or attached to the work.
+
+"Derivative Works" shall mean any work, whether in Source or Object form, that
+is based on (or derived from) the Work and for which the editorial revisions,
+annotations, elaborations, or other modifications represent, as a whole, an
+original work of authorship. For the purposes of this License, Derivative Works
+shall not include works that remain separable from, or merely link (or bind by
+name) to the interfaces of, the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including the original version
+of the Work and any modifications or additions to that Work or Derivative Works
+thereof, that is intentionally submitted to Licensor for inclusion in the Work
+by the copyright owner or by an individual or Legal Entity authorized to submit
+on behalf of the copyright owner. For the purposes of this definition,
+"submitted" means any form of electronic, verbal, or written communication sent
+to the Licensor or its representatives, including but not limited to
+communication on electronic mailing lists, source code control systems, and
+issue tracking systems that are managed by, or on behalf of, the Licensor for
+the purpose of discussing and improving the Work, but excluding communication
+that is conspicuously marked or otherwise designated in writing by the copyright
+owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity on behalf
+of whom a Contribution has been received by Licensor and subsequently
+incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of this
+License, each Contributor hereby grants to You a perpetual, worldwide,
+non-exclusive, no-charge, royalty-free, irrevocable copyright license to
+reproduce, prepare Derivative Works of, publicly display, publicly perform,
+sublicense, and distribute the Work and such Derivative Works in Source or
+Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of this License,
+each Contributor hereby grants to You a perpetual, worldwide, non-exclusive,
+no-charge, royalty-free, irrevocable (except as stated in this section) patent
+license to make, have made, use, offer to sell, sell, import, and otherwise
+transfer the Work, where such license applies only to those patent claims
+licensable by such Contributor that are necessarily infringed by their
+Contribution(s) alone or by combination of their Contribution(s) with the Work
+to which such Contribution(s) was submitted. If You institute patent litigation
+against any entity (including a cross-claim or counterclaim in a lawsuit)
+alleging that the Work or a Contribution incorporated within the Work
+constitutes direct or contributory patent infringement, then any patent licenses
+granted to You under this License for that Work shall terminate as of the date
+such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the Work or
+Derivative Works thereof in any medium, with or without modifications, and in
+Source or Object form, provided that You meet the following conditions:
+
+(a) You must give any other recipients of the Work or Derivative Works a copy of
+this License; and
+
+(b) You must cause any modified files to carry prominent notices stating that You
+changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works that You
+distribute, all copyright, patent, trademark, and attribution notices from the
+Source form of the Work, excluding those notices that do not pertain to any part
+of the Derivative Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its distribution, then
+any Derivative Works that You distribute must include a readable copy of the
+attribution notices contained within such NOTICE file, excluding those notices
+that do not pertain to any part of the Derivative Works, in at least one of the
+following places: within a NOTICE text file distributed as part of the
+Derivative Works; within the Source form or documentation, if provided along
+with the Derivative Works; or, within a display generated by the Derivative
+Works, if and wherever such third-party notices normally appear. The contents of
+the NOTICE file are for informational purposes only and do not modify the
+License. You may add Your own attribution notices within Derivative Works that
+You distribute, alongside or as an addendum to the NOTICE text from the Work,
+provided that such additional attribution notices cannot be construed as
+modifying the License.
+
+You may add Your own copyright statement to Your modifications and may provide
+additional or different license terms and conditions for use, reproduction, or
+distribution of Your modifications, or for any such Derivative Works as a whole,
+provided Your use, reproduction, and distribution of the Work otherwise complies
+with the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise, any
+Contribution intentionally submitted for inclusion in the Work by You to the
+Licensor shall be under the terms and conditions of this License, without any
+additional terms or conditions. Notwithstanding the above, nothing herein shall
+supersede or modify the terms of any separate license agreement you may have
+executed with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade names,
+trademarks, service marks, or product names of the Licensor, except as required
+for reasonable and customary use in describing the origin of the Work and
+reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or agreed to in
+writing, Licensor provides the Work (and each Contributor provides its
+Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied, including, without limitation, any warranties
+or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+PARTICULAR PURPOSE. You are solely responsible for determining the
+appropriateness of using or redistributing the Work and assume any risks
+associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory, whether in
+tor t (including negligence), contract, or otherwise, unless required by
+applicable law (such as deliberate and grossly negligent acts) or agreed to in
+writing, shall any Contributor be liable to You for damages, including any
+direct, indirect, special, incidental, or consequential damages of any character
+arising as a result of this License or out of the use or inability to use the
+Work (including but not limited to damages for loss of goodwill, work stoppage,
+computer failure or malfunction, or any and all other commercial damages or
+losses), even if such Contributor has been advised of the possibility of such
+damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing the Work or
+Derivative Works thereof, You may choose to offer, and charge a fee for,
+acceptance of support, warranty, indemnity, or other liability obligations
+and/or rights consistent with this License. However, in accepting such
+obligations, You may act only on Your own behalf and on Your sole responsibility,
+not on behalf of any other Contributor, and only if You agree to indemnify,
+defend, and hold each Contributor harmless for any liability incurred by, or
+claims asserted against, such Contributor by reason of your accepting any such
+warranty or additional liability.
+
+END OF TERMS AND CONDITIONS

dltaf-0.1.0/PKG-INFO

@@ -0,0 +1,242 @@
+Metadata-Version: 2.4
+Name: dltaf
+Version: 0.1.0
+Summary: Manifest-driven data loading toolkit with Airflow helpers and pluggable source integrations.
+Author: Pavel Kovalev
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/PaulKov/dltaf
+Project-URL: Documentation, https://paulkov.github.io/dltaf/
+Project-URL: Issues, https://github.com/PaulKov/dltaf/issues
+Project-URL: Changelog, https://github.com/PaulKov/dltaf/blob/main/CHANGELOG.md
+Keywords: airflow,clickhouse,data-engineering,dlt,etl,plugins,yaml
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Information Technology
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Database
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: System :: Distributed Computing
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: dlt[clickhouse,sql_database]<2,>=1.18.2
+Requires-Dist: PyYAML>=6.0.1
+Requires-Dist: vault-kv-client>=0.1.0
+Requires-Dist: oracledb>=2.0.0
+Requires-Dist: psycopg2-binary>=2.9.9
+Requires-Dist: pymongo>=4.6.0
+Requires-Dist: sqlalchemy>=2.0.25
+Provides-Extra: dev
+Requires-Dist: build>=1.2.2; extra == "dev"
+Requires-Dist: mkdocs>=1.6.1; extra == "dev"
+Requires-Dist: mkdocs-material>=9.6.14; extra == "dev"
+Requires-Dist: pytest>=8.3.5; extra == "dev"
+Requires-Dist: ruff>=0.11.5; extra == "dev"
+Requires-Dist: twine>=6.1.0; extra == "dev"
+Provides-Extra: docs
+Requires-Dist: mkdocs>=1.6.1; extra == "docs"
+Requires-Dist: mkdocs-material>=9.6.14; extra == "docs"
+Dynamic: license-file
+
+# dltaf
+
+`dltaf` is a manifest-driven toolkit for building repeatable data-loading pipelines with `dlt`, optional Airflow DAG generation, and a plugin-first extension model.
+
+The public package ships a clean OSS core:
+- built-in source kinds for `oracle_custom_sql`, `sql_database`, and `mongodb`
+- a unified source plugin registry
+- Airflow runtime helpers for local, packaged, and virtualenv execution
+- a Vault integration layer powered by [`vault-kv-client`](https://github.com/PaulKov/vault-kv-client)
+- documentation and examples that stay safe to publish
+
+Private integrations are intentionally not bundled into this repository. They can live in your monorepo, a private package index, or both, while still using the same `source.kind` contract.
+
+## Why dltaf
+
+- `YAML-first`: manifests stay readable and reviewable
+- `plugin-first`: internal connectors plug in without forking the OSS core
+- `Airflow-friendly`: isolated virtualenv tasks can resolve both the core package and private plugin requirements
+- `Vault-ready`: one consistent secrets contract for source and destination credentials
+- `self-service`: examples, docs, CLI inspection tools, and smoke-friendly workflows are included
+
+## Installation
+
+Runtime install:
+
+```bash
+pip install dltaf
+```
+
+Developer install:
+
+```bash
+git clone https://github.com/PaulKov/dltaf.git
+cd dltaf
+python3 -m venv .venv
+source .venv/bin/activate
+pip install -U pip
+pip install -e .[dev]
+```
+
+## Quick start
+
+Validate an example manifest:
+
+```bash
+dltaf-run --manifest dltaf/examples/manifests/smoke_sql_database_catalog.yaml --validate-only
+```
+
+Inspect available plugins:
+
+```bash
+dltaf plugins list
+dltaf plugins inspect sql_database
+dltaf plugins doctor --manifest dltaf/examples/manifests/smoke_mongodb_catalog.yaml
+```
+
+Generate Airflow DAG files from a manifests directory:
+
+```bash
+dltaf-generate-dags --manifests-dir ./manifests --output-dir ./generated_dags
+```
+
+Render lineage for a manifests directory:
+
+```bash
+dltaf-show-lineage --manifests-dir ./manifests --format mermaid
+```
+
+## Built-in source kinds
+
+### `oracle_custom_sql`
+
+Use explicit SQL files and per-query metadata:
+- one manifest can drive multiple queries
+- merge mode can enforce `primary_key`
+- SQL files stay separate from YAML
+
+### `sql_database`
+
+Use `dlt.sources.sql_database` in either:
+- single-schema mode with `schema` + `tables`
+- multi-schema mode with `schemas: {schema_name: {tables: [...]}}`
+
+### `mongodb`
+
+Use the bundled MongoDB runtime for:
+- one or many collections
+- optional collection filters and nesting control
+- replace/append behavior through the manifest `run` section
+
+## Private plugin UX
+
+The public core is designed so private connectors can stay private without degrading developer experience.
+
+### Option 1: local monorepo catalog
+
+Point `dltaf` to a local plugin catalog:
+
+```bash
+export DLTAF_PLUGIN_PATHS="/path/to/monorepo/internal/dltaf_plugins"
+dltaf plugins list
+```
+
+This is the softest rollout path when your private catalog still lives inside an existing monorepo.
+
+### Option 2: importable plugin modules
+
+Point `dltaf` to importable module names:
+
+```bash
+export DLTAF_PLUGIN_MODULES="company_private_plugins,team_connectors"
+dltaf plugins list
+```
+
+### Option 3: installed private packages
+
+Install a private package that exposes entry points in the `dltaf.plugins` group. `dltaf` will discover them automatically.
+
+### Plugin contract
+
+Every plugin registers one or more `SourcePlugin` objects with:
+- `kind`
+- `validate(manifest)`
+- `build_runtime_env(manifest)` if needed
+- `run(manifest)`
+
+Canonical recommendation for private kinds:
+
+```text
+internal.customer_export
+internal.partner_events
+company.some_connector
+```
+
+### Scaffold a new plugin
+
+```bash
+dltaf scaffold plugin --kind internal.customer_export --output-dir ./internal/dltaf_plugins
+```
+
+## Airflow
+
+`dltaf` ships Airflow helpers for:
+- generating DAGs from manifests
+- loading `run_manifest()` inside standard or virtualenv tasks
+- propagating plugin paths, plugin modules, and plugin-specific requirements to isolated runtimes
+
+Useful runtime environment variables:
+- `DLTAF_PACKAGE_ROOT`
+- `DLTAF_PLUGIN_PATHS`
+- `DLTAF_PLUGIN_MODULES`
+- `DLTAF_PLUGIN_REQUIREMENTS`
+
+See the full guide in [GitHub Pages](https://paulkov.github.io/dltaf/airflow/).
+
+## Vault integration
+
+`dltaf` resolves manifest Vault references through `vault-kv-client`.
+
+Supported reference forms:
+- `vault://mount/path`
+- `mount:path`
+- mapping form with `mount_point`, `path`, and optional `kv_version`
+
+This keeps the secrets contract stable across local runs, CI, and Airflow.
+
+## Examples
+
+The repository ships sanitized examples under `dltaf/examples/`:
+- `smoke_oracle_custom_sql.yaml`
+- `smoke_sql_database_catalog.yaml`
+- `smoke_mongodb_catalog.yaml`
+
+They are intentionally generic. Replace the sample Vault refs and connection settings with your own environment before running them against a live system.
+
+## Documentation
+
+Full docs live on GitHub Pages:
+
+- Docs: https://paulkov.github.io/dltaf/
+- Plugin guide: https://paulkov.github.io/dltaf/plugins/
+- Airflow guide: https://paulkov.github.io/dltaf/airflow/
+- Examples: https://paulkov.github.io/dltaf/examples/
+
+## Development
+
+Run the standard checks locally:
+
+```bash
+ruff check .
+pytest
+python -m build
+mkdocs build
+```
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE).

dltaf-0.1.0/README.md

@@ -0,0 +1,198 @@
+# dltaf
+
+`dltaf` is a manifest-driven toolkit for building repeatable data-loading pipelines with `dlt`, optional Airflow DAG generation, and a plugin-first extension model.
+
+The public package ships a clean OSS core:
+- built-in source kinds for `oracle_custom_sql`, `sql_database`, and `mongodb`
+- a unified source plugin registry
+- Airflow runtime helpers for local, packaged, and virtualenv execution
+- a Vault integration layer powered by [`vault-kv-client`](https://github.com/PaulKov/vault-kv-client)
+- documentation and examples that stay safe to publish
+
+Private integrations are intentionally not bundled into this repository. They can live in your monorepo, a private package index, or both, while still using the same `source.kind` contract.
+
+## Why dltaf
+
+- `YAML-first`: manifests stay readable and reviewable
+- `plugin-first`: internal connectors plug in without forking the OSS core
+- `Airflow-friendly`: isolated virtualenv tasks can resolve both the core package and private plugin requirements
+- `Vault-ready`: one consistent secrets contract for source and destination credentials
+- `self-service`: examples, docs, CLI inspection tools, and smoke-friendly workflows are included
+
+## Installation
+
+Runtime install:
+
+```bash
+pip install dltaf
+```
+
+Developer install:
+
+```bash
+git clone https://github.com/PaulKov/dltaf.git
+cd dltaf
+python3 -m venv .venv
+source .venv/bin/activate
+pip install -U pip
+pip install -e .[dev]
+```
+
+## Quick start
+
+Validate an example manifest:
+
+```bash
+dltaf-run --manifest dltaf/examples/manifests/smoke_sql_database_catalog.yaml --validate-only
+```
+
+Inspect available plugins:
+
+```bash
+dltaf plugins list
+dltaf plugins inspect sql_database
+dltaf plugins doctor --manifest dltaf/examples/manifests/smoke_mongodb_catalog.yaml
+```
+
+Generate Airflow DAG files from a manifests directory:
+
+```bash
+dltaf-generate-dags --manifests-dir ./manifests --output-dir ./generated_dags
+```
+
+Render lineage for a manifests directory:
+
+```bash
+dltaf-show-lineage --manifests-dir ./manifests --format mermaid
+```
+
+## Built-in source kinds
+
+### `oracle_custom_sql`
+
+Use explicit SQL files and per-query metadata:
+- one manifest can drive multiple queries
+- merge mode can enforce `primary_key`
+- SQL files stay separate from YAML
+
+### `sql_database`
+
+Use `dlt.sources.sql_database` in either:
+- single-schema mode with `schema` + `tables`
+- multi-schema mode with `schemas: {schema_name: {tables: [...]}}`
+
+### `mongodb`
+
+Use the bundled MongoDB runtime for:
+- one or many collections
+- optional collection filters and nesting control
+- replace/append behavior through the manifest `run` section
+
+## Private plugin UX
+
+The public core is designed so private connectors can stay private without degrading developer experience.
+
+### Option 1: local monorepo catalog
+
+Point `dltaf` to a local plugin catalog:
+
+```bash
+export DLTAF_PLUGIN_PATHS="/path/to/monorepo/internal/dltaf_plugins"
+dltaf plugins list
+```
+
+This is the softest rollout path when your private catalog still lives inside an existing monorepo.
+
+### Option 2: importable plugin modules
+
+Point `dltaf` to importable module names:
+
+```bash
+export DLTAF_PLUGIN_MODULES="company_private_plugins,team_connectors"
+dltaf plugins list
+```
+
+### Option 3: installed private packages
+
+Install a private package that exposes entry points in the `dltaf.plugins` group. `dltaf` will discover them automatically.
+
+### Plugin contract
+
+Every plugin registers one or more `SourcePlugin` objects with:
+- `kind`
+- `validate(manifest)`
+- `build_runtime_env(manifest)` if needed
+- `run(manifest)`
+
+Canonical recommendation for private kinds:
+
+```text
+internal.customer_export
+internal.partner_events
+company.some_connector
+```
+
+### Scaffold a new plugin
+
+```bash
+dltaf scaffold plugin --kind internal.customer_export --output-dir ./internal/dltaf_plugins
+```
+
+## Airflow
+
+`dltaf` ships Airflow helpers for:
+- generating DAGs from manifests
+- loading `run_manifest()` inside standard or virtualenv tasks
+- propagating plugin paths, plugin modules, and plugin-specific requirements to isolated runtimes
+
+Useful runtime environment variables:
+- `DLTAF_PACKAGE_ROOT`
+- `DLTAF_PLUGIN_PATHS`
+- `DLTAF_PLUGIN_MODULES`
+- `DLTAF_PLUGIN_REQUIREMENTS`
+
+See the full guide in [GitHub Pages](https://paulkov.github.io/dltaf/airflow/).
+
+## Vault integration
+
+`dltaf` resolves manifest Vault references through `vault-kv-client`.
+
+Supported reference forms:
+- `vault://mount/path`
+- `mount:path`
+- mapping form with `mount_point`, `path`, and optional `kv_version`
+
+This keeps the secrets contract stable across local runs, CI, and Airflow.
+
+## Examples
+
+The repository ships sanitized examples under `dltaf/examples/`:
+- `smoke_oracle_custom_sql.yaml`
+- `smoke_sql_database_catalog.yaml`
+- `smoke_mongodb_catalog.yaml`
+
+They are intentionally generic. Replace the sample Vault refs and connection settings with your own environment before running them against a live system.
+
+## Documentation
+
+Full docs live on GitHub Pages:
+
+- Docs: https://paulkov.github.io/dltaf/
+- Plugin guide: https://paulkov.github.io/dltaf/plugins/
+- Airflow guide: https://paulkov.github.io/dltaf/airflow/
+- Examples: https://paulkov.github.io/dltaf/examples/
+
+## Development
+
+Run the standard checks locally:
+
+```bash
+ruff check .
+pytest
+python -m build
+mkdocs build
+```
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE).

dltaf-0.1.0/cli/__init__.py

@@ -0,0 +1,23 @@
+"""CLI утилиты для управления dlt пайплайнами и Airflow DAG'ами.
+
+Этот пакет содержит производственные command-line инструменты для работы с dlt:
+  - show_lineage: Визуализация и анализ зависимостей между пайплайнами (lineage graph)
+  - generate_dags: Автоматическая генерация Airflow DAG файлов из YAML манифестов
+
+Примеры использования:
+    # Показать lineage (граф зависимостей пайплайнов)
+    python -m cli.show_lineage
+    python -m cli.show_lineage --format json      # JSON формат для программной обработки
+    python -m cli.show_lineage --format mermaid   # Mermaid диаграмма для визуализации
+
+    # Генерация Airflow DAG файлов из YAML манифестов
+    python -m cli.generate_dags                   # инкрементальная генерация
+    python -m cli.generate_dags --clean           # удалить старые DAG'и, сгенерировать заново
+
+    # Через установленные CLI команды (после pip install -e .):
+    dlt-show-lineage
+    dlt-show-lineage --format mermaid
+    dlt-generate-dags --clean
+"""
+
+__all__ = ["show_lineage", "generate_dags"]