dbt-labs / dbt-labs/dbt-jobs-as-code

Add more checks when people use the flow to import jobs created manually

Open
#139 0 comments 0 reactions 1 assignee Claimed by @b-per View on GitHub
bug triage
Dominant language
Python
Stars
85
Forks
14
Avg merge
16m
Merged PRs (30d)
5

Description

If we have a `staging` and `prod` env, the tool can be used so that jobs are created manually in `staging` and they can be promoted to `prod` using `import-jobs` and `plan`/`sync`.

But once some jobs have been promoted the `import-jobs` need to be filtering on the specific `staging` env id, otherwise changes done in `staging` to already moved to `prod` jobs are not getting reflected.

We should provider some warnings/errors and path to resolution when we realize that the `import-jobs` filter is missing the env filter.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.