@@ -49,7 +49,7 @@ Run this if you need to do a real clone of the `prod` and `prep` databases. This
#### `clone_raw_full`
Run this if you need to run extract, freshness, or snapshot jobs. Subsequent runs of this job will be fast as it only verifies if the clone exists.
Run this if you need to run extract or freshness jobs. Subsequent runs of this job will be fast as it only verifies if the clone exists.
#### `clone_raw_postgres_pipeline`
@@ -215,16 +215,6 @@ You should run this pipeline manually when either `*.md` or `.yml` files are cha
These jobs are defined in [`snowflake-dbt-ci.yml`](https://gitlab.com/gitlab-data/analytics/-/blob/master/transform/snowflake-dbt/snowflake-dbt-ci.yml)
#### `🧠all_tests`
Runs all the tests
- Note: it is not necessary to run this job if you've run any of the dbt_run stage jobs as tests are included.
#### `💾data_tests`
Runs only data tests
#### `🔍ds_exposure_dependencies_query`
This CI job runs automatically whenever SQL files in the dbt project are updated. It checks if any modified models are tied to Data Science exposures and, if so, fails the job while notifying the user. It is then the MR creator’s responsibility to inform the Data Science team, ensuring they have the opportunity to review any potential impact.
@@ -323,22 +313,6 @@ The MNPI exception tag `mnpi_exception` can be added to the model if it does not
Automatically runs when making changes in the snowflake-dbt/macros folder and checks if the newly created macros match the correct name format.
#### `🗂schema_tests`
Runs only schema tests
#### `📸snapshots`
Runs snapshots. This jobs runs against the clone of `RAW`. Requires the `clone_raw_full` job to have been run.
#### `📝specify_tests`
Runs specified model tests with the variable `DBT_MODELS`
#### `🌱manual_seed`
Runs a full seed operation. For use to confirm results when working on changes to the dbt seeds themselves.
#### `run_grants`
Run this if you'd like to grant access to the copies or clones of `prep` and `prod` for your branch to your role or a role of a business partner. Specify the snowflake roles (see [roles.yml](https://gitlab.com/gitlab-data/analytics/-/blob/master/permissions/snowflake/roles.yml)) you'd like to grant access to using the `GRANT_TO_ROLES` CI variable. You can pass in a single role, or multiple separated by a space as in `role1 role2`. This job checks the git commit for the changed models and verifies that the submitted roles have adequate access in `PREP` and `PROD` to grant access in the clone. It does not create any future grants and so **all relevant objects must be built in the clone before you run this job if you want to ensure adequate object grants.**
