gen3-dataops-toolkit 3.1.0__tar.gz → 3.2.0__tar.gz

{gen3_dataops_toolkit-3.1.0 → gen3_dataops_toolkit-3.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: gen3-dataops-toolkit
-Version: 3.1.0
+Version: 3.2.0
 Summary: Gen3 DataOps toolkit (g3dt): operate SSM-published Gen3 data pipeline environments
 License: Apache-2.0
 Author: JoshuaHarris391
@@ -113,13 +113,13 @@ structurally impossible.
 
 **Only the dbt template's `ci` target is prefixed.** `g3dt config dbt-env`
 emits, alongside the real names, the CI-isolation variants the template's
-`ci` target consumes: `G3DT_DB_BRONZE_CI` / `G3DT_DB_SILVER_CI` /
-`G3DT_DB_GOLD_CI` (`ci_` + the real database name) and
-`G3DT_S3_BRONZE_DATA_DIR_CI` / `G3DT_S3_SILVER_DATA_DIR_CI` /
-`G3DT_S3_GOLD_DATA_DIR_CI` (`dbt_ci/` under the same buckets). Bronze can be
-dbt-managed from gen3-dbt-template's synthetic-data revision onwards; a
-pipeline deployment >= v2.1.0 provides the matching `ci_..._bronze_db` Glue
-database. Toolkit
+`ci` target consumes: `G3DT_DB_SILVER_CI` / `G3DT_DB_GOLD_CI`
+(`ci_` + the real database name) and `G3DT_S3_SILVER_DATA_DIR_CI` /
+`G3DT_S3_GOLD_DATA_DIR_CI` (`dbt_ci/` under the same buckets). Bronze is
+ingest-only — dbt never writes it, and the template's synthetic demo data
+generates at silver — so bronze gets only `G3DT_DB_BRONZE` (real-ingest
+deployments resolve their sources.yml schema from it); pairs with an
+aws-gen3-pipeline deployment >= v2.2.0. Toolkit
 releases >= 3 read the raw-free medallion SSM keys and therefore require a
 pipeline deployment >= v2.0.0, which publishes them. Commit-
 triggered CI builds land there; every other target (default, local) and the

{gen3_dataops_toolkit-3.1.0 → gen3_dataops_toolkit-3.2.0}/README.md

@@ -79,13 +79,13 @@ structurally impossible.
 
 **Only the dbt template's `ci` target is prefixed.** `g3dt config dbt-env`
 emits, alongside the real names, the CI-isolation variants the template's
-`ci` target consumes: `G3DT_DB_BRONZE_CI` / `G3DT_DB_SILVER_CI` /
-`G3DT_DB_GOLD_CI` (`ci_` + the real database name) and
-`G3DT_S3_BRONZE_DATA_DIR_CI` / `G3DT_S3_SILVER_DATA_DIR_CI` /
-`G3DT_S3_GOLD_DATA_DIR_CI` (`dbt_ci/` under the same buckets). Bronze can be
-dbt-managed from gen3-dbt-template's synthetic-data revision onwards; a
-pipeline deployment >= v2.1.0 provides the matching `ci_..._bronze_db` Glue
-database. Toolkit
+`ci` target consumes: `G3DT_DB_SILVER_CI` / `G3DT_DB_GOLD_CI`
+(`ci_` + the real database name) and `G3DT_S3_SILVER_DATA_DIR_CI` /
+`G3DT_S3_GOLD_DATA_DIR_CI` (`dbt_ci/` under the same buckets). Bronze is
+ingest-only — dbt never writes it, and the template's synthetic demo data
+generates at silver — so bronze gets only `G3DT_DB_BRONZE` (real-ingest
+deployments resolve their sources.yml schema from it); pairs with an
+aws-gen3-pipeline deployment >= v2.2.0. Toolkit
 releases >= 3 read the raw-free medallion SSM keys and therefore require a
 pipeline deployment >= v2.0.0, which publishes them. Commit-
 triggered CI builds land there; every other target (default, local) and the

{gen3_dataops_toolkit-3.1.0 → gen3_dataops_toolkit-3.2.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "gen3-dataops-toolkit"
-version = "3.1.0"
+version = "3.2.0"
 description = "Gen3 DataOps toolkit (g3dt): operate SSM-published Gen3 data pipeline environments"
 authors = ["JoshuaHarris391 <harjo391@gmail.com>"]
 readme = "README.md"

{gen3_dataops_toolkit-3.1.0 → gen3_dataops_toolkit-3.2.0}/src/g3dt/cli/config_cmds.py

@@ -233,7 +233,6 @@ def dbt_env(
         gold_db = _req_key(rc, "glue/db/gold")
         silver_bucket = _req_key(rc, "buckets/silver")
         gold_bucket = _req_key(rc, "buckets/gold")
-        bronze_bucket = _req_key(rc, "buckets/bronze")
         bronze_db = _req_key(rc, "glue/db/bronze")
     except config.ConfigError as exc:
         typer.secho(str(exc), fg=typer.colors.RED, err=True)
@@ -246,16 +245,15 @@ def dbt_env(
         "G3DT_DB_BRONZE": bronze_db,
         "G3DT_DB_SILVER": silver_db,
         "G3DT_DB_GOLD": gold_db,
-        "G3DT_S3_BRONZE_DATA_DIR": f"s3://{bronze_bucket}/dbt/",
         "G3DT_S3_SILVER_DATA_DIR": f"s3://{silver_bucket}/dbt/",
         "G3DT_S3_GOLD_DATA_DIR": f"s3://{gold_bucket}/dbt/",
         # CI isolation: the dbt template's `ci` target builds into these
         # instead — same grammar as the CDK's ci_ databases, same buckets
         # under a dbt_ci/ prefix. Real names above are never prefixed.
-        "G3DT_DB_BRONZE_CI": f"ci_{bronze_db}",
+        # Bronze has no CI variants: bronze is ingest-only (never written
+        # by dbt), so only its real database name is exported.
         "G3DT_DB_SILVER_CI": f"ci_{silver_db}",
         "G3DT_DB_GOLD_CI": f"ci_{gold_db}",
-        "G3DT_S3_BRONZE_DATA_DIR_CI": f"s3://{bronze_bucket}/dbt_ci/",
         "G3DT_S3_SILVER_DATA_DIR_CI": f"s3://{silver_bucket}/dbt_ci/",
         "G3DT_S3_GOLD_DATA_DIR_CI": f"s3://{gold_bucket}/dbt_ci/",
     }