Create "API" tag for those issues requesting flags and operators, and dbt version strategy

[dinigo]

Hi, there's a number of issues asking for this and that new flag or param in new dbt versions. It'd be nice to tag them as such, they're nice "first contributions".

There's still the pending issue of supporting newer dbt versions. Do we want to suppport all the dbt versions? do we want to be tied to the Airflow version (see #54 ) or to the dbt version (see #59 ), or to both, using a compat matrix like dbt-utils.

Maybe the render function should also receive the airflow version it is rendering against.

Another option would be to do just like the Airflow providers does, they do NOT support old airflow versions. I think it makes sense to support dbt v1.x officially in airflow-dbt. And also look into adding this as a provider at some point

[andrewrjones]

Thanks for the suggestion on the label, I've added it and tagged the issues!

Good question on the versioning. Hmm, not sure what is best really. I think it's ok for newer versions of the library to drop support for older versions of Airflow fairly quickly, and similar for dbt. There are not loads of new features being added to this library, so odds are if you are using an older version of either Airflow or dbt you can continue to use an older version of this library without issues.

Let's think about this a bit more :)