Adapter specific versions of Postgres, Redshift, and Bigquery

Follows from Move to adapter-specific installations of dbt (... (#3105 - closed)

This issue is planned as a follow-up to the initial dbt-snowflake release.

To have parity, we likely need these three:

• dbt-postgres
• dbt-redshift
• dbt-bigquery

Possible:

• `dbt-spark[PyHive]
• dbt-presto

Full list of dbt Labs supported adapters https://docs.getdbt.com/docs/available-adapters

set weight to 8

mentioned in issue #3105 (closed)

changed the description

added kindFeature valuestreamMeltano labels

changed milestone to %May 2022

added to epic &82

mentioned in issue #3300 (closed)

marked this issue as related to #3098 (closed)

removed the relation with #3098 (closed)

marked this issue as related to #3098 (closed)

added OKR: Be the DataOps OS Roadmap labels

changed milestone to %April 2022

changed milestone to %May 2022

mentioned in issue #3345 (closed)

mentioned in merge request !2523 (closed)

mentioned in issue #2989 (closed)

changed title from Adapter specific versions of Postgres, Redshift, and Postgres to Adapter specific versions of Postgres, Redshift, and Bigquery

assigned to @kgpayne

assigned to @cjohnhanson and unassigned @kgpayne

@cjohnhanson - As discussed, I'm happy for you to pick this up as it would be good exposure to how Meltano will be working with dbt in the new model, along with exposure to the legacy situation for context.

The two three four moving peices to be aware of:

1. This technically has not landed yet, although it is very close: !2593 (merged)
2. This will change how target is applied: Active Environment Name As Env Variable (#3377 - closed)
3. The "stable" experience will be to have these plugin entries on the hub and installed/locked when @edgarrmondragon ships Support `meltano add` directly from Hub (#3283 - closed)
4. The ability to register these in the Hub is being worked on by @alex1126 in Add support for hosting 'utilities' and 'files'... (hub#202 - closed)

3 and 4 are good context to know of, but only 1 and 2 will really impact your design work, I think. I've assigned to April 18 iteration so the dust can settle a little bit (the week after next), but you can pull in earlier if you feel you are ready to work it.

Cc @kgpayne - Can you partner with @cjohnhanson on this as needed? I think he can probably work in parallel with your handling #3377 (closed) and any docs refinement.

mentioned in issue #3407 (closed)

marked this issue as related to #3407 (closed)

marked this issue as related to #3105 (closed)

mentioned in issue #3423 (closed)

added v2.0 label

mentioned in merge request !2642 (merged)

changed iteration to WK May 9, 2022 - May 15, 2022

marked this issue as related to #3489 (closed)

changed iteration to WK May 16, 2022 - May 22, 2022

added flowReview label

mentioned in issue #3504 (closed)

mentioned in commit 45ce4ea9

closed with merge request !2642 (merged)