Benoit Perigaud

**Describe the feature** There is an open PR to allow running the tool on specific project ids or env ids **Describe alternatives you've considered** Now that we have `production` and...

Solves #20 Adding logic to cancel the job that was triggered if the action is still running when we cancel it. It can be useful when `workflow_dispatch` is used, but...

Add support for global connections credentials for previous "adapter-style" connections

1

e.g. spark and fabric/synapse

Support for the [model level notifications feature](https://docs.getdbt.com/docs/deploy/model-notifications) The feature is still in Beta but will be released soon

Add a new macro to cast all columns based on data types in YAML

1

### Describe the feature Add a macro to automatically cast all the columns to the types defined in the YAML config. Today, when creating a a model with a contract,...

Improve some of the logging to make it easier to understand what might be wrong. For example: - if there is no job returned - if the `account_id` and/or `project_id`...

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`...

[Feature] Allow more advanced configuration of output for the `plan` (and maybe `sync`) commands

4

The following could be useful: - [ ] Allow showing or not the individual jobs changes along with the "summary" table to stdout - [ ] Provide output with advanced...

[Feature] Provide the ability to post the results of the `plan` to GitHub, as a comment

1

Today, people have to go through the CI/CD logs in order to see if changes have been identified as part of a `plan` on PR creation. We should provide a...