datahub-yaml-source 0.1.0__tar.gz

datahub_yaml_source-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,109 @@
+# Contributing
+
+Thanks for considering a contribution to `datahub-yaml-source`.
+
+## Development setup
+
+Supported Python versions: 3.10, 3.11, 3.12 (the floor tracked in `setup.py`'s
+`python_requires`, matching `acryl-datahub`'s own Python >=3.10 requirement).
+CI (`.github/workflows/ci.yml`) runs the test suite on all three.
+
+```bash
+pip install -e ".[dev]"
+```
+
+This installs the connector in editable mode and registers the `yaml` source
+type with `acryl-datahub` via a `datahub.ingestion.source.plugins` entry
+point. Verify it's picked up with:
+
+```bash
+datahub check plugins
+```
+
+## Running the tests
+
+```bash
+pytest tests/unit                 # unit tests
+pytest tests/integration          # integration test against a curated fixture,
+                                   # golden-file checked
+```
+
+If you intentionally change the connector's output, refresh the integration
+golden file and review the diff by hand before committing it:
+
+```bash
+pytest tests/integration/yaml_source/test_yaml_source_golden.py --update-golden-files
+```
+
+## Regenerating derived docs
+
+`docs/sources/yaml/reference.md` and
+`docs/sources/yaml/schema/yaml-metadata.schema.json` are generated from the
+Pydantic models in `src/datahub_yaml_source/models.py`. Any change to those
+models must be followed by:
+
+```bash
+python scripts/generate_json_schema.py
+python scripts/generate_markdown_docs.py
+```
+
+`tests/unit/test_json_schema_generation.py` and
+`tests/unit/test_markdown_docs_generation.py` fail if these artifacts are out
+of sync with the models, so this step is not optional.
+
+## Adding a new `kind:` or aspect
+
+A new document kind or a new field typically touches: the Pydantic model in
+`models.py`, the relevant builder in `src/datahub_yaml_source/builders/`,
+`urns.py` for any new URN helper, `loader.py` / `yaml_source.py` /
+`yaml_source_report.py` for a brand-new kind, the regenerated docs above, unit
+tests for the model and builder, and an addition to the integration fixture
+tree under `tests/integration/yaml_source/resources/` with a refreshed golden
+file.
+
+See `_PLANNING.md` for the architecture rationale (why SDK V2 vs. raw MCP per
+kind, emission ordering, reference-resolution strategy).
+
+## Code style
+
+- No SQL parsing, no live connection: this source's entire job is translating
+  declarative YAML into DataHub metadata. Keep new code consistent with that
+  scope.
+- Prefer DataHub's SDK V2 (`datahub.sdk.*`) where a wrapper exists for the
+  entity type; fall back to `MetadataChangeProposalWrapper` otherwise. Never
+  use the legacy MCE API.
+- A malformed or unresolvable document should produce a warning on the
+  ingestion report and be skipped, not crash the whole run, unless
+  `fail_on_unresolved_reference` is set.
+
+### Lint, format, and types
+
+Ruff and mypy are installed by the `dev` extra. Before pushing, run the same
+checks CI runs (`.github/workflows/quality.yml`, contract in
+`spec/spec-process-cicd-quality.md`):
+
+```bash
+ruff check .            # lint (blocking in CI)
+ruff format --check .   # formatting (blocking in CI); drop --check to apply
+mypy                    # type check over src/ (blocking in CI)
+```
+
+`ruff check --fix .` auto-fixes most lint findings. `ruff` config
+(`[tool.ruff]`, line length 100, target `py310`) and `mypy` config
+(`[tool.mypy]`, `src/` only, non-strict) both live in `pyproject.toml`. The mypy
+baseline is zero — `mypy` must exit clean before a PR can merge. Fix a new error
+with a real annotation/guard; a `# type: ignore[<code>]` is a last resort and
+needs a one-line reason.
+
+## Submitting changes
+
+1. Open an issue or discussion first for anything beyond a small fix, so the
+   approach can be agreed before you invest time in it.
+2. Keep pull requests focused — one logical change per PR.
+3. Make sure `pytest tests/unit tests/integration` passes and that generated
+   docs/schema are committed alongside any model change.
+4. Describe *why* the change is needed, not just what it does — the commit
+   message and PR description should stand on their own.
+
+By contributing, you agree that your contributions will be licensed under the
+project's [Apache License 2.0](LICENSE).

datahub_yaml_source-0.1.0/LICENSE

@@ -0,0 +1,190 @@
+                                 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
+      (an example is provided in the Appendix below).
+
+      "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 tort (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
+
+   Copyright 2026 Assistance Publique - Hopitaux de Paris (AP-HP)
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

datahub_yaml_source-0.1.0/MANIFEST.in

@@ -0,0 +1,20 @@
+# setuptools-scm (pyproject.toml [tool.setuptools_scm]) turns on a file
+# finder that otherwise sweeps *every* Git-tracked path into the sdist.
+# Keep the sdist to what a consumer of the package actually needs; the
+# rest lives on GitHub.
+
+prune tests
+prune docs
+prune spec
+prune scripts
+prune .github
+
+exclude AGENTS.md
+exclude CLAUDE.md
+exclude _PLANNING.md
+exclude skills-lock.json
+exclude bash.exe.stackdump
+exclude .gitignore
+
+include LICENSE
+include README.md

datahub_yaml_source-0.1.0/PKG-INFO

@@ -0,0 +1,124 @@
+Metadata-Version: 2.4
+Name: datahub-yaml-source
+Version: 0.1.0
+Summary: DataHub ingestion source that reads declarative YAML metadata files.
+Home-page: https://github.com/davidouagne/datahub-yaml-source
+Author: David Ouagne
+Author-email: david.ouagne@aphp.fr
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/davidouagne/datahub-yaml-source
+Project-URL: Issues, https://github.com/davidouagne/datahub-yaml-source/issues
+Project-URL: Changelog, https://github.com/davidouagne/datahub-yaml-source/releases
+Keywords: datahub,metadata,ingestion,yaml,metadata-as-code,data-catalog
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Information Technology
+Classifier: License :: OSI Approved :: Apache Software License
+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
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: acryl-datahub<1.8,>=1.7.0.9
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: pydantic<3.0.0,>=2.4.0
+Requires-Dist: requests<3,>=2.28.0
+Provides-Extra: git
+Requires-Dist: GitPython<4,>=3.1.37; extra == "git"
+Provides-Extra: s3
+Requires-Dist: boto3<2,>=1.35.0; extra == "s3"
+Provides-Extra: dev
+Requires-Dist: pytest>=7.0.0; extra == "dev"
+Requires-Dist: pytest-cov>=4.0.0; extra == "dev"
+Requires-Dist: deepdiff>=6.0.0; extra == "dev"
+Requires-Dist: jsonschema>=4.0.0; extra == "dev"
+Requires-Dist: GitPython<4,>=3.1.37; extra == "dev"
+Requires-Dist: boto3<2,>=1.35.0; extra == "dev"
+Requires-Dist: ruff<0.17,>=0.12; extra == "dev"
+Requires-Dist: mypy>=1.17; extra == "dev"
+Requires-Dist: types-PyYAML>=6.0; extra == "dev"
+Dynamic: author
+Dynamic: author-email
+Dynamic: classifier
+Dynamic: description
+Dynamic: description-content-type
+Dynamic: home-page
+Dynamic: keywords
+Dynamic: license
+Dynamic: license-file
+Dynamic: project-url
+Dynamic: provides-extra
+Dynamic: requires-dist
+Dynamic: requires-python
+Dynamic: summary
+
+# datahub-yaml-source
+
+[![CI](https://github.com/davidouagne/datahub-yaml-source/actions/workflows/ci.yml/badge.svg)](https://github.com/davidouagne/datahub-yaml-source/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/datahub-yaml-source)](https://pypi.org/project/datahub-yaml-source/)
+[![Python versions](https://img.shields.io/badge/python-3.10%20%7C%203.11%20%7C%203.12-blue)](https://pypi.org/project/datahub-yaml-source/)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://github.com/davidouagne/datahub-yaml-source/blob/main/LICENSE)
+
+A standalone [DataHub](https://datahubproject.io/) ingestion source plugin that
+reads a directory tree of declarative YAML "metadata as code" files and emits
+the DataHub entities they describe (platforms, tags, glossary, domains,
+containers, datasets with schema/lineage, data products, pipelines, pipeline
+run history, and data quality assertions).
+
+See [docs/sources/yaml/yaml.md](https://github.com/davidouagne/datahub-yaml-source/blob/main/docs/sources/yaml/yaml.md) for a narrative
+introduction, [docs/sources/yaml/reference.md](https://github.com/davidouagne/datahub-yaml-source/blob/main/docs/sources/yaml/reference.md)
+for a generated field-by-field reference of every `kind`, and
+[docs/sources/yaml/yaml_recipe.yml](https://github.com/davidouagne/datahub-yaml-source/blob/main/docs/sources/yaml/yaml_recipe.yml) for an
+example recipe. See [_PLANNING.md](https://github.com/davidouagne/datahub-yaml-source/blob/main/_PLANNING.md) for the architecture
+decisions behind this connector.
+
+A [JSON Schema](https://github.com/davidouagne/datahub-yaml-source/blob/main/docs/sources/yaml/schema/yaml-metadata.schema.json) for the
+document format (autocomplete/validation in VS Code, IntelliJ, ...) is also
+generated from the Pydantic models -- see the "Editor autocomplete and
+validation" section in `yaml.md`.
+
+Both `reference.md` and the JSON Schema are generated from
+`src/datahub_yaml_source/models.py`; regenerate them after changing a model:
+
+```bash
+python scripts/generate_json_schema.py
+python scripts/generate_markdown_docs.py
+```
+
+## Installation
+
+```bash
+pip install -e .
+```
+
+This registers the `yaml` source type with `acryl-datahub` via a
+`datahub.ingestion.source.plugins` entry point. Verify it's picked up with:
+
+```bash
+datahub check plugins
+```
+
+## Usage
+
+```bash
+datahub ingest -c docs/sources/yaml/yaml_recipe.yml
+```
+
+## Development
+
+```bash
+pip install -e ".[dev]"
+pytest tests/unit                 # unit tests
+pytest tests/integration          # integration test against a curated fixture,
+                                   # golden-file checked
+```
+
+To regenerate the integration golden file after an intentional output change:
+
+```bash
+pytest tests/integration/yaml_source/test_yaml_source_golden.py --update-golden-files
+```

datahub_yaml_source-0.1.0/README.md

@@ -0,0 +1,66 @@
+# datahub-yaml-source
+
+[![CI](https://github.com/davidouagne/datahub-yaml-source/actions/workflows/ci.yml/badge.svg)](https://github.com/davidouagne/datahub-yaml-source/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/datahub-yaml-source)](https://pypi.org/project/datahub-yaml-source/)
+[![Python versions](https://img.shields.io/badge/python-3.10%20%7C%203.11%20%7C%203.12-blue)](https://pypi.org/project/datahub-yaml-source/)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://github.com/davidouagne/datahub-yaml-source/blob/main/LICENSE)
+
+A standalone [DataHub](https://datahubproject.io/) ingestion source plugin that
+reads a directory tree of declarative YAML "metadata as code" files and emits
+the DataHub entities they describe (platforms, tags, glossary, domains,
+containers, datasets with schema/lineage, data products, pipelines, pipeline
+run history, and data quality assertions).
+
+See [docs/sources/yaml/yaml.md](https://github.com/davidouagne/datahub-yaml-source/blob/main/docs/sources/yaml/yaml.md) for a narrative
+introduction, [docs/sources/yaml/reference.md](https://github.com/davidouagne/datahub-yaml-source/blob/main/docs/sources/yaml/reference.md)
+for a generated field-by-field reference of every `kind`, and
+[docs/sources/yaml/yaml_recipe.yml](https://github.com/davidouagne/datahub-yaml-source/blob/main/docs/sources/yaml/yaml_recipe.yml) for an
+example recipe. See [_PLANNING.md](https://github.com/davidouagne/datahub-yaml-source/blob/main/_PLANNING.md) for the architecture
+decisions behind this connector.
+
+A [JSON Schema](https://github.com/davidouagne/datahub-yaml-source/blob/main/docs/sources/yaml/schema/yaml-metadata.schema.json) for the
+document format (autocomplete/validation in VS Code, IntelliJ, ...) is also
+generated from the Pydantic models -- see the "Editor autocomplete and
+validation" section in `yaml.md`.
+
+Both `reference.md` and the JSON Schema are generated from
+`src/datahub_yaml_source/models.py`; regenerate them after changing a model:
+
+```bash
+python scripts/generate_json_schema.py
+python scripts/generate_markdown_docs.py
+```
+
+## Installation
+
+```bash
+pip install -e .
+```
+
+This registers the `yaml` source type with `acryl-datahub` via a
+`datahub.ingestion.source.plugins` entry point. Verify it's picked up with:
+
+```bash
+datahub check plugins
+```
+
+## Usage
+
+```bash
+datahub ingest -c docs/sources/yaml/yaml_recipe.yml
+```
+
+## Development
+
+```bash
+pip install -e ".[dev]"
+pytest tests/unit                 # unit tests
+pytest tests/integration          # integration test against a curated fixture,
+                                   # golden-file checked
+```
+
+To regenerate the integration golden file after an intentional output change:
+
+```bash
+pytest tests/integration/yaml_source/test_yaml_source_golden.py --update-golden-files
+```

datahub_yaml_source-0.1.0/pyproject.toml

@@ -0,0 +1,70 @@
+# setup.py still holds the package metadata (deps, extras, entry points);
+# this file adds the PEP 517 build-system and the tool config that Ruff,
+# mypy and setuptools-scm look for here first. The package version is not
+# written anywhere -- setuptools-scm derives it from Git tags at build
+# time (see [tool.setuptools_scm] below and
+# spec/spec-process-cicd-quality.md / spec-process-cicd-ci.md for the CI
+# `fetch-depth: 0` this needs).
+
+[build-system]
+requires = ["setuptools>=84.0.0", "setuptools-scm>=10.2.3,<11"]
+build-backend = "setuptools.build_meta"
+
+[tool.setuptools_scm]
+# no-guess-dev: an untagged commit is X.Y.Z.post1.devN (explicitly "after
+#   the last release"), not X.Y.(Z+1).devN which would imply an unreleased
+#   future version that may never ship.
+# no-local-version: drop the +g<hash> local segment -- PyPI / TestPyPI
+#   reject local versions, so any non-tag build (e.g. a CI dev upload)
+#   stays valid. Clean tag builds are unaffected either way.
+# fallback_version: a build from a source archive with no .git and no
+#   SETUPTOOLS_SCM_PRETEND_VERSION degrades to 0.0.0 instead of hard-failing.
+version_scheme = "no-guess-dev"
+local_scheme = "no-local-version"
+fallback_version = "0.0.0"
+
+[tool.ruff]
+line-length = 100
+target-version = "py310"
+src = ["src", "tests", "scripts"]
+# Ruff's scope here is first-party Python only. Since 0.16 `ruff format` also
+# reformats ```python blocks inside Markdown; the illustrative snippets in
+# `_PLANNING.md` are hand-shaped for reading, so keep prose docs out.
+extend-exclude = ["*.md"]
+
+[tool.ruff.lint]
+# Pragmatic set for a solo-maintained translation layer: pyflakes/pycodestyle
+# errors (E, F), import sorting (I), pyupgrade (UP), flake8-bugbear (B),
+# flake8-comprehensions (C4), flake8-simplify (SIM) and Ruff's own rules
+# (RUF). Deliberately excludes annotation-completeness (ANN) and the
+# opinionated pylint (PL) families to keep the signal high.
+select = ["E", "F", "I", "UP", "B", "C4", "SIM", "RUF"]
+
+[tool.ruff.lint.per-file-ignores]
+# Re-export surfaces: an unused import is the point.
+"__init__.py" = ["F401"]
+# Test fixtures embed full DataHub URNs and JSON blobs as string literals;
+# these are legitimately long and not meaningfully breakable. The formatter
+# still enforces 100 cols on everything it can reflow.
+"tests/**" = ["E501"]
+
+[tool.ruff.lint.isort]
+known-first-party = ["datahub_yaml_source"]
+
+[tool.mypy]
+# Advisory only -- the quality workflow runs this job with
+# continue-on-error. Scope is the package itself; tests/ and scripts/ are
+# left out until the src/ signal is clean. Non-strict baseline, with the
+# few low-noise warnings that catch real staleness.
+files = ["src"]
+python_version = "3.10"
+check_untyped_defs = true
+warn_unused_ignores = true
+warn_redundant_casts = true
+
+[[tool.mypy.overrides]]
+# acryl-datahub ships partial/absent type information; its generated
+# metadata classes in particular are untyped. Don't let that drown the
+# signal from our own code.
+module = ["datahub.*", "deepdiff.*"]
+ignore_missing_imports = true

datahub_yaml_source-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+