dbt-labs/dbt-jobs-as-code

Issues

• [Feature] Add ability to "link" existing jobs to jobs managed by dbt-jobs-as-code

  #107 opened a month ago by b-per
  0

• [Feature] Add the ability to set notifications from dbt-jobs-as-code

  #77 opened 6 months ago by b-per
  1

• [Bug] incompatibility of importlib-metadata

  #93 opened 3 months ago by rsong24
  1

• [BUG] Error 400: Invalid Request Due to Unexpected Property custom_branch_only

  #91 opened 3 months ago by sedukulla
  5

• [Feature] Return a non 0 code when dbt-jobs-as-code fails

  #79 opened 5 months ago by b-per
  0

• [Feature] seperate environment management

  #64 opened 6 months ago by chenxuanrong
  2

• Improve overall performance of the tool

  #36 opened 6 months ago by b-per
  2

• [Feature] Allow setting up "trigger on job completion" (i.e. job chaining)

  #69 opened 6 months ago by b-per
  0

• [Feature] Add ability to template jobs for different environments and "promote" jobs

  #70 opened 6 months ago by b-per
  0

• [Feature] Allow running the tool with a combination of project id and env type

  #68 opened 7 months ago by b-per
  0

• [Feature] Update User Agent to identify API calls from this library

  #65 opened 7 months ago by b-per
  0

• [Bug] Missing `custom_branch_only` from retrieved dbt Cloud job config

  #59 opened a year ago by lewisarmistead
  4

• [Bug] Deferred Environment not included when using `import-jobs`

  #56 opened a year ago by brunocostalopes
  3

• Capability to create dbt cloud environments

  #54 opened a year ago by venkata-varanasi
  3

• [Feature] Do you want to put the JSON Schema in dbt-jsonschema?

  #52 opened 2 years ago by joellabes
  0

• Create a Github Action for the library

  #40 opened 2 years ago by b-per
  1

• Refactor tests to leverage fixtures

  #48 opened 2 years ago by b-per
  0

• Check that env vars exist in the `validate` command

  #27 opened 2 years ago by b-per
  0

• When the config is changed provide more information about the value before/after

  #35 opened 2 years ago by b-per
  1

• Refactor validation code into functions

  #26 opened 2 years ago by b-per
  0

• Simplify the logic of updating/deleting env var overwrite using sets

  #19 opened 2 years ago by b-per
  0

• Add `pytest` suite to ensure that the package works and to ease future upgrade

  #11 opened 2 years ago by b-per
  0

• Need issue templates for Features and Bugs.

  #43 opened 2 years ago by nicholasyager
  0

• Implement CustomEnvironmentVariable creation

  #20 opened 2 years ago by nicholasyager
  1

• Revise typing of env vars and `update_env_var()` in particular

  #18 opened 2 years ago by b-per
  0

• Add proper command line support for specifying the jobs.yml file

  #9 opened 2 years ago by nicholasyager
  0

• Revise optional/default fields for our JobDefinition

  #5 opened 2 years ago by b-per
  2

• Get the Account ID either from an env var or reading from the YML file

  #2 opened 2 years ago by b-per
  0

• Provide the ability to "import" jobs setup from the UI as job-as-code

  #28 opened 2 years ago by b-per
  0

• Provide a `plan` command like Terraform

  #29 opened 2 years ago by b-per
  0

• Create a JSON schema spec for the YML file

  #6 opened 2 years ago by b-per
  0

• BUG - Currently deleting an env_var value from a job doesn't delete the env var overwrite

  #25 opened 2 years ago by b-per
  0

• Pydantic validations

  #23 opened 2 years ago by b-per
  0

• Add a `validator` or `apply` command to check that the current YAML file is correct

  #12 opened 2 years ago by b-per
  0

• Dig on the correct syntax for `schedule`

  #4 opened 2 years ago by b-per
  1

• Add a command to check the validity of the current config

  #22 opened 2 years ago by b-per
  0

• Support overwriting env vars at the job level

  #13 opened 2 years ago by b-per
  0

• Investigate: `generate_sources` doesn't seem to do anything, we use `run_generate_sources` instead

  #3 opened 2 years ago by b-per
  0