datajunction 0.0.250__tar.gz → 0.0.251__tar.gz

{datajunction-0.0.250 → datajunction-0.0.251}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: datajunction
-Version: 0.0.250
+Version: 0.0.251
 Summary: DataJunction client library for connecting to a DataJunction server
 Project-URL: repository, https://github.com/DataJunction/dj
 Author-email: DataJunction Authors <yian.shang@gmail.com>

{datajunction-0.0.250 → datajunction-0.0.251}/datajunction/__about__.py

@@ -2,4 +2,4 @@
 Version for Hatch
 """
 
-__version__ = "0.0.250"
+__version__ = "0.0.251"

{datajunction-0.0.250 → datajunction-0.0.251}/datajunction/deployment.py

@@ -593,6 +593,12 @@ class DeploymentService:
         if "managed_tag_types" in project_metadata:
             deployment_spec["managed_tag_types"] = project_metadata["managed_tag_types"]
 
+        if "checks" in project_metadata:
+            deployment_spec["checks"] = project_metadata["checks"]
+
+        if "rulesets" in project_metadata:
+            deployment_spec["rulesets"] = project_metadata["rulesets"]
+
         # Add deployment source if available from env vars
         source = self._build_deployment_source(cwd=base_dir)
         if source:  # pragma: no branch

{datajunction-0.0.250 → datajunction-0.0.251}/tests/test_deploy.py

@@ -185,6 +185,53 @@ def test_reconstruct_deployment_spec_forwards_managed_tag_types(tmp_path):
     assert spec["managed_tag_types"] == ["domain"]
 
 
+def test_reconstruct_deployment_spec_forwards_checks_and_rulesets(tmp_path):
+    """`checks:` and `rulesets:` in dj.yaml reach the deployment payload.
+
+    Same defect as custom_metadata_schemas: the payload names its keys one by
+    one, so a manifest section nobody named is read and dropped. Dropped here
+    it fails silently -- the deploy succeeds having evaluated nothing.
+    """
+    (tmp_path / "dj.yaml").write_text(
+        "namespace: ns\n"
+        "checks:\n"
+        "  - name: demo.described\n"
+        "    description: Every node has a description.\n"
+        "    condition: \"node.description != ''\"\n"
+        "    gate: warn\n"
+        "rulesets:\n"
+        "  - name: baseline\n"
+        "    checks: [demo.described]\n",
+    )
+    (tmp_path / "revenue.yaml").write_text(
+        "name: ns.revenue\nnode_type: metric\nquery: SELECT SUM(amount) FROM ns.fct\n",
+    )
+
+    svc = DeploymentService(MagicMock())
+    spec, _ = svc._reconstruct_deployment_spec(tmp_path)
+
+    assert [check["name"] for check in spec["checks"]] == ["demo.described"]
+    assert spec["rulesets"] == [{"name": "baseline", "checks": ["demo.described"]}]
+
+
+def test_reconstruct_deployment_spec_omits_absent_checks(tmp_path):
+    """A manifest that declares no checks must not send the key.
+
+    Absent leaves the namespace's governance alone; [] would say this manifest
+    manages checks and declares none.
+    """
+    (tmp_path / "dj.yaml").write_text("namespace: ns\n")
+    (tmp_path / "revenue.yaml").write_text(
+        "name: ns.revenue\nnode_type: metric\nquery: SELECT SUM(amount) FROM ns.fct\n",
+    )
+
+    svc = DeploymentService(MagicMock())
+    spec, _ = svc._reconstruct_deployment_spec(tmp_path)
+
+    assert "checks" not in spec
+    assert "rulesets" not in spec
+
+
 def test_reconstruct_deployment_spec_omits_absent_managed_tag_types(tmp_path):
     """A manifest with no claims must not send the key: [] would release them."""
     (tmp_path / "dj.yaml").write_text("namespace: ns\n")