update to use Docs object

.bumpversion.cfg

@@ -1,5 +1,5 @@
 [bumpversion]
-current_version = 1.3.0b2
+current_version = 1.3.0a1
 parse = (?P<major>\d+)
 	\.(?P<minor>\d+)
 	\.(?P<patch>\d+)

.changes/1.3.0-b1.md

@@ -1,38 +0,0 @@
-## dbt-core 1.3.0-b1 - July 29, 2022
-### Features
-- Python model inital version ([#5261](https://github.com/dbt-labs/dbt-core/issues/5261), [#5421](https://github.com/dbt-labs/dbt-core/pull/5421))
-- allows user to include the file extension for .py models in the dbt run -m command. ([#5289](https://github.com/dbt-labs/dbt-core/issues/5289), [#5295](https://github.com/dbt-labs/dbt-core/pull/5295))
-- Incremental materialization refactor and cleanup ([#5245](https://github.com/dbt-labs/dbt-core/issues/5245), [#5359](https://github.com/dbt-labs/dbt-core/pull/5359))
-- Python models can support incremental logic ([#0](https://github.com/dbt-labs/dbt-core/issues/0), [#35](https://github.com/dbt-labs/dbt-core/pull/35))
-- Add reusable function for retrying adapter connections. Utilize said function to add retries for Postgres (and Redshift). ([#5022](https://github.com/dbt-labs/dbt-core/issues/5022), [#5432](https://github.com/dbt-labs/dbt-core/pull/5432))
-- add exponential backoff to connection retries on Postgres (and Redshift) ([#5502](https://github.com/dbt-labs/dbt-core/issues/5502), [#5503](https://github.com/dbt-labs/dbt-core/pull/5503))
-### Fixes
-- Add context to compilation errors generated while rendering generic test configuration values. ([#5294](https://github.com/dbt-labs/dbt-core/issues/5294), [#5393](https://github.com/dbt-labs/dbt-core/pull/5393))
-- Rename try to strict for more intuitiveness ([#5475](https://github.com/dbt-labs/dbt-core/issues/5475), [#5477](https://github.com/dbt-labs/dbt-core/pull/5477))
-- Ignore empty strings passed in as secrets ([#5312](https://github.com/dbt-labs/dbt-core/issues/5312), [#5518](https://github.com/dbt-labs/dbt-core/pull/5518))
-- Fix handling of top-level exceptions ([#5564](https://github.com/dbt-labs/dbt-core/issues/5564), [#5560](https://github.com/dbt-labs/dbt-core/pull/5560))
-### Docs
-- Update dependency inline-source from ^6.1.5 to ^7.2.0 ([#5574](https://github.com/dbt-labs/dbt-core/issues/5574), [#5577](https://github.com/dbt-labs/dbt-core/pull/5577))
-- Update dependency jest from ^26.2.2 to ^28.1.3 ([#5574](https://github.com/dbt-labs/dbt-core/issues/5574), [#5577](https://github.com/dbt-labs/dbt-core/pull/5577))
-- Update dependency underscore from ^1.9.0 to ^1.13.4 ([#5574](https://github.com/dbt-labs/dbt-core/issues/5574), [#5577](https://github.com/dbt-labs/dbt-core/pull/5577))
-- Update dependency webpack-cli from ^3.3.12 to ^4.7.0 ([#5574](https://github.com/dbt-labs/dbt-core/issues/5574), [#5577](https://github.com/dbt-labs/dbt-core/pull/5577))
-- Update dependency webpack-dev-server from ^3.1.11 to ^4.9.3 ([#5574](https://github.com/dbt-labs/dbt-core/issues/5574), [#5577](https://github.com/dbt-labs/dbt-core/pull/5577))
-- Searches no longer require perfect matches, and instead consider each word individually. `my model` or `model my` will now find `my_model`, without the need for underscores ([#5574](https://github.com/dbt-labs/dbt-core/issues/5574), [#5577](https://github.com/dbt-labs/dbt-core/pull/5577))
-- Support the renaming of SQL to code happening in dbt-core ([#5574](https://github.com/dbt-labs/dbt-core/issues/5574), [#5577](https://github.com/dbt-labs/dbt-core/pull/5577))
-### Under the Hood
-- Added language to tracked fields in run_model event ([#5571](https://github.com/dbt-labs/dbt-core/issues/5571), [#5469](https://github.com/dbt-labs/dbt-core/pull/5469))
-- Update mashumaro to 3.0.3 ([#4940](https://github.com/dbt-labs/dbt-core/issues/4940), [#5118](https://github.com/dbt-labs/dbt-core/pull/5118))
-- Add python incremental materialization test ([#0000](https://github.com/dbt-labs/dbt-core/issues/0000), [#5571](https://github.com/dbt-labs/dbt-core/pull/5571))
-### Dependencies
-- Upgrade to Jinja2==3.1.2 from Jinja2==2.11.3 ([#4748](https://github.com/dbt-labs/dbt-core/issues/4748), [#5465](https://github.com/dbt-labs/dbt-core/pull/5465))
-- Bump mypy from 0.961 to 0.971 ([#4904](https://github.com/dbt-labs/dbt-core/issues/4904), [#5495](https://github.com/dbt-labs/dbt-core/pull/5495))
-- Remove pin for MarkUpSafe from >=0.23,<2.1 ([#5506](https://github.com/dbt-labs/dbt-core/issues/5506), [#5507](https://github.com/dbt-labs/dbt-core/pull/5507))
-
-### Contributors
-- [@Goodkat](https://github.com/Goodkat) ([#5518](https://github.com/dbt-labs/dbt-core/pull/5518))
-- [@drewbanin](https://github.com/drewbanin) ([#5577](https://github.com/dbt-labs/dbt-core/pull/5577))
-- [@jeremyyeo](https://github.com/jeremyyeo) ([#5477](https://github.com/dbt-labs/dbt-core/pull/5477))
-- [@joellabes](https://github.com/joellabes) ([#5577](https://github.com/dbt-labs/dbt-core/pull/5577))
-- [@leoebfolsom](https://github.com/leoebfolsom) ([#5295](https://github.com/dbt-labs/dbt-core/pull/5295))
-- [@nicholasyager](https://github.com/nicholasyager) ([#5393](https://github.com/dbt-labs/dbt-core/pull/5393))
-- [@tomasfarias](https://github.com/tomasfarias) ([#5432](https://github.com/dbt-labs/dbt-core/pull/5432))

.changes/1.3.0-b2.md

@@ -1,49 +0,0 @@
-## dbt-core 1.3.0-b2 - August 29, 2022
-
-### Features
-
-- Add `--defer` flag to dbt compile & dbt docs generate ([#4110](https://github.com/dbt-labs/dbt-core/issues/4110), [#4514](https://github.com/dbt-labs/dbt-core/pull/4514))
-- use MethodName.File when value ends with .csv ([#5578](https://github.com/dbt-labs/dbt-core/issues/5578), [#5581](https://github.com/dbt-labs/dbt-core/pull/5581))
-- Make `docs` configurable in `dbt_project.yml` and add a `node_color` attribute to change the color of nodes in the DAG ([#5333](https://github.com/dbt-labs/dbt-core/issues/5333), [#5397](https://github.com/dbt-labs/dbt-core/pull/5397))
-- Adding ResolvedMetricReference helper functions and tests ([#5567](https://github.com/dbt-labs/dbt-core/issues/5567), [#5607](https://github.com/dbt-labs/dbt-core/pull/5607))
-- Check dbt-core version requirements when installing Hub packages ([#5648](https://github.com/dbt-labs/dbt-core/issues/5648), [#5651](https://github.com/dbt-labs/dbt-core/pull/5651))
-
-### Fixes
-
-- Remove the default 256 characters limit on postgres character varying type when no limitation is set ([#5238](https://github.com/dbt-labs/dbt-core/issues/5238), [#5292](https://github.com/dbt-labs/dbt-core/pull/5292))
-- Include schema file config in unrendered_config ([#5338](https://github.com/dbt-labs/dbt-core/issues/5338), [#5344](https://github.com/dbt-labs/dbt-core/pull/5344))
-- Resolves #5351 - Do not consider shorter varchar cols as schema changes ([#5351](https://github.com/dbt-labs/dbt-core/issues/5351), [#5395](https://github.com/dbt-labs/dbt-core/pull/5395))
-- on_shchma_change fail verbosity enhancement ([#5504](https://github.com/dbt-labs/dbt-core/issues/5504), [#5505](https://github.com/dbt-labs/dbt-core/pull/5505))
-- Fix error rendering docs block in metrics description ([#5585](https://github.com/dbt-labs/dbt-core/issues/5585), [#5603](https://github.com/dbt-labs/dbt-core/pull/5603))
-- Extended validations for the project names ([#5379](https://github.com/dbt-labs/dbt-core/issues/5379), [#5620](https://github.com/dbt-labs/dbt-core/pull/5620))
-- Use sys.exit instead of exit ([#5621](https://github.com/dbt-labs/dbt-core/issues/5621), [#5627](https://github.com/dbt-labs/dbt-core/pull/5627))
-- Finishing logic upgrade to Redshift for name truncation collisions. ([#5586](https://github.com/dbt-labs/dbt-core/issues/5586), [#5656](https://github.com/dbt-labs/dbt-core/pull/5656))
-- multiple args for ref and source ([#5634](https://github.com/dbt-labs/dbt-core/issues/5634), [#5635](https://github.com/dbt-labs/dbt-core/pull/5635))
-- Fix Unexpected behavior when chaining methods on dbt-ref'ed/sourced dataframes ([#5646](https://github.com/dbt-labs/dbt-core/issues/5646), [#5677](https://github.com/dbt-labs/dbt-core/pull/5677))
-
-### Docs
-
-- Leverages `docs.node_color` from `dbt-core` to color nodes in the DAG ([dbt-docs/#44](https://github.com/dbt-labs/dbt-docs/issues/44), [dbt-docs/#281](https://github.com/dbt-labs/dbt-docs/pull/281))
-
-### Under the Hood
-
-- Save use of default env vars to manifest to enable partial parsing in those cases. ([#5155](https://github.com/dbt-labs/dbt-core/issues/5155), [#5589](https://github.com/dbt-labs/dbt-core/pull/5589))
-- add more information to log line interop test failures ([#5658](https://github.com/dbt-labs/dbt-core/issues/5658), [#5659](https://github.com/dbt-labs/dbt-core/pull/5659))
-- Add supported languages to materializations ([#5569](https://github.com/dbt-labs/dbt-core/issues/5569), [#5695](https://github.com/dbt-labs/dbt-core/pull/5695))
-
-### Dependency
-
-- Bump python from 3.10.5-slim-bullseye to 3.10.6-slim-bullseye in /docker ([#4904](https://github.com/dbt-labs/dbt-core/issues/4904), [#5623](https://github.com/dbt-labs/dbt-core/pull/5623))
-- Bump mashumaro[msgpack] from 3.0.3 to 3.0.4 in /core ([#4904](https://github.com/dbt-labs/dbt-core/issues/4904), [#5649](https://github.com/dbt-labs/dbt-core/pull/5649))
-
-### Contributors
-- [@Goodkat](https://github.com/Goodkat) ([#5581](https://github.com/dbt-labs/dbt-core/pull/5581), [#5620](https://github.com/dbt-labs/dbt-core/pull/5620))
-- [@Ilanbenb](https://github.com/Ilanbenb) ([#5505](https://github.com/dbt-labs/dbt-core/pull/5505))
-- [@b-per](https://github.com/b-per) ([#5397](https://github.com/dbt-labs/dbt-core/pull/5397), [dbt-docs/#281](https://github.com/dbt-labs/dbt-docs/pull/281))
-- [@callum-mcdata](https://github.com/callum-mcdata) ([#5607](https://github.com/dbt-labs/dbt-core/pull/5607))
-- [@epapineau](https://github.com/epapineau) ([#5395](https://github.com/dbt-labs/dbt-core/pull/5395))
-- [@kadero](https://github.com/kadero) ([#4514](https://github.com/dbt-labs/dbt-core/pull/4514))
-- [@matt-winkler](https://github.com/matt-winkler) ([#5397](https://github.com/dbt-labs/dbt-core/pull/5397), [dbt-docs/#281](https://github.com/dbt-labs/dbt-docs/pull/281))
-- [@shrodingers](https://github.com/shrodingers) ([#5292](https://github.com/dbt-labs/dbt-core/pull/5292))
-- [@sungchun12](https://github.com/sungchun12) ([#5397](https://github.com/dbt-labs/dbt-core/pull/5397), [dbt-docs/#281](https://github.com/dbt-labs/dbt-docs/pull/281))
-- [@varun-dc](https://github.com/varun-dc) ([#5627](https://github.com/dbt-labs/dbt-core/pull/5627))

.changes/1.3.0/Dependencies-20220719-141646.yaml

@@ -1,7 +0,0 @@
-kind: Dependencies
-body: Upgrade to Jinja2==3.1.2 from Jinja2==2.11.3
-time: 2022-07-19T14:16:46.665631-05:00
-custom:
-  Author: emmyoop
-  Issue: "4748"
-  PR: "5465"

.changes/1.3.0/Dependencies-20220720-000741.yaml

@@ -1,7 +0,0 @@
-kind: Dependencies
-body: "Bump mypy from 0.961 to 0.971"
-time: 2022-07-20T00:07:41.000000-05:00
-custom:
-  Author: dependabot[bot]
-  Issue: "4904"
-  PR: "5495"

.changes/1.3.0/Dependencies-20220721-093233.yaml

@@ -1,7 +0,0 @@
-kind: Dependencies
-body: Remove pin for MarkUpSafe from >=0.23,<2.1
-time: 2022-07-21T09:32:33.494002-05:00
-custom:
-  Author: emmyoop
-  Issue: "5506"
-  PR: "5507"

.changes/1.3.0/Dependency-20220808-132327.yaml

@@ -1,7 +0,0 @@
-kind: Dependency
-body: "Bump python from 3.10.5-slim-bullseye to 3.10.6-slim-bullseye in /docker"
-time: 2022-08-08T13:23:27.00000Z
-custom:
-  Author: dependabot[bot]
-  Issue: 4904
-  PR: 5623

.changes/1.3.0/Dependency-20220815-182731.yaml

@@ -1,7 +0,0 @@
-kind: Dependency
-body: "Bump mashumaro[msgpack] from 3.0.3 to 3.0.4 in /core"
-time: 2022-08-15T18:27:31.00000Z
-custom:
-  Author: dependabot[bot]
-  Issue: 4904
-  PR: 5649

.changes/1.3.0/Docs-20220728-140258.yaml

@@ -1,7 +0,0 @@
-kind: Docs
-body: Update dependency inline-source from ^6.1.5 to ^7.2.0
-time: 2022-07-28T14:02:58.441963-07:00
-custom:
-  Author: emmyoop
-  Issue: "299"
-  PR: "291"

.changes/1.3.0/Docs-20220728-140329.yaml

@@ -1,7 +0,0 @@
-kind: Docs
-body: Update dependency jest from ^26.2.2 to ^28.1.3
-time: 2022-07-28T14:03:29.837274-07:00
-custom:
-  Author: emmyoop
-  Issue: "299"
-  PR: "291"

.changes/1.3.0/Docs-20220728-140351.yaml

@@ -1,7 +0,0 @@
-kind: Docs
-body: Update dependency underscore from ^1.9.0 to ^1.13.4
-time: 2022-07-28T14:03:51.123441-07:00
-custom:
-  Author: emmyoop
-  Issue: "299"
-  PR: "291"

.changes/1.3.0/Docs-20220728-140425.yaml

@@ -1,7 +0,0 @@
-kind: Docs
-body: Update dependency webpack-cli from ^3.3.12 to ^4.7.0
-time: 2022-07-28T14:04:25.629638-07:00
-custom:
-  Author: emmyoop
-  Issue: "299"
-  PR: "291"

.changes/1.3.0/Docs-20220728-140449.yaml

@@ -1,7 +0,0 @@
-kind: Docs
-body: Update dependency webpack-dev-server from ^3.1.11 to ^4.9.3
-time: 2022-07-28T14:04:49.637369-07:00
-custom:
-  Author: emmyoop
-  Issue: "299"
-  PR: "291"

.changes/1.3.0/Docs-20220728-140620.yaml

@@ -1,8 +0,0 @@
-kind: Docs
-body: Searches no longer require perfect matches, and instead consider each word individually.
-  `my model` or `model my` will now find `my_model`, without the need for underscores
-time: 2022-07-28T14:06:20.371364-07:00
-custom:
-  Author: joellabes
-  Issue: "143"
-  PR: "145"

.changes/1.3.0/Docs-20220728-140806.yaml

@@ -1,7 +0,0 @@
-kind: Docs
-body: Support the renaming of SQL to code happening in dbt-core
-time: 2022-07-28T14:08:06.184934-07:00
-custom:
-  Author: jtcohen6 stu-k drewbanin ChenyuLInx
-  Issue: "299"
-  PR: "292"

.changes/1.3.0/Docs-20220804-134138.yaml

@@ -1,7 +0,0 @@
-kind: Docs
-body: Leverages `docs.node_color` from `dbt-core` to color nodes in the DAG
-time: 2022-08-04T13:41:38.669987-05:00
-custom:
-  Author: matt-winkler sungchun12 b-per
-  Issue: "44"
-  PR: "281"

.changes/1.3.0/Features-20220314-181127.yaml

@@ -1,7 +0,0 @@
-kind: Features
-body: Add `--defer` flag to dbt compile & dbt docs generate
-time: 2022-03-14T18:11:27.783107864+01:00
-custom:
-  Author: kadero
-  Issue: "4110"
-  PR: "4514"

.changes/1.3.0/Features-20220510-165130.yaml

@@ -1,7 +0,0 @@
-kind: Features
-body: Python model inital version
-time: 2022-05-10T16:51:30.245589-07:00
-custom:
-  Author: ChenyuLInx
-  Issue: "5261"
-  PR: "5421"

.changes/1.3.0/Features-20220526-165323.yaml

@@ -1,7 +0,0 @@
-kind: Features
-body: allows user to include the file extension for .py models in the dbt run -m command.
-time: 2022-05-26T16:53:23.389671-07:00
-custom:
-  Author: leoebfolsom
-  Issue: "5289"
-  PR: "5295"

.changes/1.3.0/Features-20220610-105647.yaml

@@ -1,7 +0,0 @@
-kind: Features
-body: Incremental materialization refactor and cleanup
-time: 2022-06-10T10:56:47.226887-04:00
-custom:
-  Author: gshank
-  Issue: "5245"
-  PR: "5359"

.changes/1.3.0/Features-20220627-131042.yaml

@@ -1,7 +0,0 @@
-kind: Features
-body: Python models can support incremental logic
-time: 2022-06-27T13:10:42.123303-05:00
-custom:
-  Author: iknox-fa
-  Issue: "0"
-  PR: "35"

.changes/1.3.0/Features-20220720-171257.yaml

@@ -1,7 +0,0 @@
-kind: Features
-body: add exponential backoff to connection retries on Postgres (and Redshift)
-time: 2022-07-20T17:12:57.486949-04:00
-custom:
-  Author: nathaniel-may
-  Issue: "5502"
-  PR: "5503"

.changes/1.3.0/Features-20220729-173231.yaml

@@ -1,7 +0,0 @@
-kind: Features
-body: use MethodName.File when value ends with .csv
-time: 2022-07-29T17:32:31.395677157+02:00
-custom:
-  Author: Goodkat
-  Issue: "5578"
-  PR: "5581"

.changes/1.3.0/Features-20220803-104230.yaml

@@ -1,8 +0,0 @@
-kind: Features
-body: Make `docs` configurable in `dbt_project.yml` and add a `node_color` attribute
-  to change the color of nodes in the DAG
-time: 2022-08-03T10:42:30.60624+02:00
-custom:
-  Author: matt-winkler sungchun12 b-per
-  Issue: "5333"
-  PR: "5397"

.changes/1.3.0/Features-20220804-120936.yaml

@@ -1,7 +0,0 @@
-kind: Features
-body: Adding ResolvedMetricReference helper functions and tests
-time: 2022-08-04T12:09:36.202919-04:00
-custom:
-  Author: callum-mcdata
-  Issue: "5567"
-  PR: "5607"

.changes/1.3.0/Features-20220815-134312.yaml

@@ -1,7 +0,0 @@
-kind: Features
-body: Check dbt-core version requirements when installing Hub packages
-time: 2022-08-15T13:43:12.965143+01:00
-custom:
-  Author: jtcohen6
-  Issue: "5648"
-  PR: "5651"

.changes/1.3.0/Fixes-20220523-103843.yaml

@@ -1,8 +0,0 @@
-kind: Fixes
-body: Remove the default 256 characters limit on postgres character varying type when
-  no limitation is set
-time: 2022-05-23T10:38:43.392232+02:00
-custom:
-  Author: shrodingers
-  Issue: "5238"
-  PR: "5292"

.changes/1.3.0/Fixes-20220607-123058.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: Include schema file config in unrendered_config
-time: 2022-06-07T12:30:58.535207-04:00
-custom:
-  Author: gshank
-  Issue: "5338"
-  PR: "5344"

.changes/1.3.0/Fixes-20220617-193731.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: 'Resolves #5351 - Do not consider shorter varchar cols as schema changes'
-time: 2022-06-17T19:37:31.885484-07:00
-custom:
-  Author: epapineau
-  Issue: "5351"
-  PR: "5395"

.changes/1.3.0/Fixes-20220720-213746.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: on_shchma_change fail verbosity enhancement
-time: 2022-07-20T21:37:46.474241+03:00
-custom:
-  Author: Ilanbenb
-  Issue: "5504"
-  PR: "5505"

.changes/1.3.0/Fixes-20220723-215330.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: Ignore empty strings passed in as secrets
-time: 2022-07-23T21:53:30.907759094+02:00
-custom:
-  Author: Goodkat
-  Issue: "5312"
-  PR: "5518"

.changes/1.3.0/Fixes-20220726-113636.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: Fix handling of top-level exceptions
-time: 2022-07-26T11:36:36.824979-04:00
-custom:
-  Author: gshank
-  Issue: "5564"
-  PR: "5560"

.changes/1.3.0/Fixes-20220803-144221.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: Fix error rendering docs block in metrics description
-time: 2022-08-03T14:42:21.386265-04:00
-custom:
-  Author: gshank
-  Issue: "5585"
-  PR: "5603"

.changes/1.3.0/Fixes-20220805-221022.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: Extended validations for the project names
-time: 2022-08-05T22:10:22.746830854+02:00
-custom:
-  Author: Goodkat
-  Issue: "5379"
-  PR: "5620"

.changes/1.3.0/Fixes-20220808-112001.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: Use sys.exit instead of exit
-time: 2022-08-08T11:20:01.838171926-04:00
-custom:
-  Author: varun-dc
-  Issue: "5621"
-  PR: "5627"

.changes/1.3.0/Fixes-20220815-230409.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: Finishing logic upgrade to Redshift for name truncation collisions.
-time: 2022-08-15T23:04:09.173645-07:00
-custom:
-  Author: versusfacit
-  Issue: "5586"
-  PR: "5656"

.changes/1.3.0/Fixes-20220816-153401.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: multiple args for ref and source
-time: 2022-08-16T15:34:01.348339-07:00
-custom:
-  Author: ChenyuLInx
-  Issue: "5634"
-  PR: "5635"

.changes/1.3.0/Fixes-20220817-163642.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: Fix Unexpected behavior when chaining methods on dbt-ref'ed/sourced dataframes
-time: 2022-08-17T16:36:42.678275-07:00
-custom:
-  Author: ChenyuLInx
-  Issue: "5646"
-  PR: "5677"

.changes/1.3.0/Under the Hood-20220617-150744.yaml

@@ -1,8 +0,0 @@
-kind: Fixes
-body: Add context to compilation errors generated while rendering generic test configuration
-  values.
-time: 2022-06-17T15:07:44.751037-04:00
-custom:
-  Author: nicholasyager
-  Issue: "5294"
-  PR: "5393"

.changes/1.3.0/Under the Hood-20220713-124925.yaml

@@ -1,7 +0,0 @@
-kind: Under the Hood
-body: Added language to tracked fields in run_model event
-time: 2022-07-13T12:49:25.362678-05:00
-custom:
-  Author: stu-k
-  Issue: "5571"
-  PR: "5469"

.changes/1.3.0/Under the Hood-20220720-115226.yaml

@@ -1,7 +0,0 @@
-kind: Under the Hood
-body: Update mashumaro to 3.0.3
-time: 2022-07-20T11:52:26.210876-04:00
-custom:
-  Author: gshank
-  Issue: "4940"
-  PR: "5118"

.changes/1.3.0/Under the Hood-20220728-094536.yaml

@@ -1,7 +0,0 @@
-kind: Under the Hood
-body: Add python incremental materialization test
-time: 2022-07-28T09:45:36.13608-05:00
-custom:
-  Author: stu-k
-  Issue: "0000"
-  PR: "5571"

.changes/1.3.0/Under the Hood-20220802-112936.yaml

@@ -1,8 +0,0 @@
-kind: Under the Hood
-body: Save use of default env vars to manifest to enable partial parsing in those
-  cases.
-time: 2022-08-02T11:29:36.417589-05:00
-custom:
-  Author: emmyoop
-  Issue: "5155"
-  PR: "5589"

.changes/1.3.0/Under the Hood-20220816-122032.yaml

@@ -1,7 +0,0 @@
-kind: Under the Hood
-body: add more information to log line interop test failures
-time: 2022-08-16T12:20:32.119588+01:00
-custom:
-  Author: nathaniel-may
-  Issue: "5658"
-  PR: "5659"

.changes/1.3.0/Under the Hood-20220822-103739.yaml

@@ -1,7 +0,0 @@
-kind: Under the Hood
-body: Add supported languages to materializations
-time: 2022-08-22T10:37:39.50743-05:00
-custom:
-  Author: stu-k
-  Issue: "5569"
-  PR: "5695"

.changes/unreleased/Breaking Changes-20220906-154521.yaml

@@ -1,7 +0,0 @@
-kind: Breaking Changes
-body: Renaming Metric Spec Attributes
-time: 2022-09-06T15:45:21.2769-05:00
-custom:
-  Author: callum-mcdata
-  Issue: "5774"
-  PR: "5775"

.changes/unreleased/Dependency-20220906-134858.yaml

@@ -1,7 +0,0 @@
-kind: "Dependency"
-body: "Bump black from 22.6.0 to 22.8.0"
-time: 2022-09-06T13:48:58.00000Z
-custom:
-  Author: dependabot[bot]
-  Issue: 4904
-  PR: 5750

.changes/unreleased/Dependency-20220912-002253.yaml

@@ -1,7 +0,0 @@
-kind: "Dependency"
-body: "Bump python from 3.10.6-slim-bullseye to 3.10.7-slim-bullseye in /docker"
-time: 2022-09-12T00:22:53.00000Z
-custom:
-  Author: dependabot[bot]
-  Issue: 4904
-  PR: 5805

.changes/unreleased/Features-20220831-121319.yaml

@@ -1,7 +0,0 @@
-kind: Features
-body: Adding the `window` parameter to the metric spec.
-time: 2022-08-31T12:13:19.48356-05:00
-custom:
-  Author: callum-mcdata
-  Issue: "5721"
-  PR: "5722"

.changes/unreleased/Features-20220908-081315.yaml

@@ -1,7 +0,0 @@
-kind: Features
-body: Add invocation args dict to ProviderContext class
-time: 2022-09-08T08:13:15.17337+01:00
-custom:
-  Author: jared-rimmer
-  Issue: "5524"
-  PR: "5782"

.changes/unreleased/Features-20220908-104149.yaml

@@ -1,7 +0,0 @@
-kind: Features
-body: Adds new cli framework
-time: 2022-09-08T10:41:49.375734-05:00
-custom:
-  Author: iknox-fa
-  Issue: "5526"
-  PR: "5647"

.changes/unreleased/Features-20220913-095924.yaml

@@ -1,7 +0,0 @@
-kind: Features
-body: Add enabled config to exposures and metrics
-time: 2022-09-13T09:59:24.445918-05:00
-custom:
-  Author: emmyoop
-  Issue: "5422"
-  PR: "5815"

.changes/unreleased/Fixes-20220823-112633.yaml

@@ -1,8 +0,0 @@
-kind: Fixes
-body: Include py.typed in MANIFEST.in. This enables packages that install dbt-core
-  from pypi to use mypy.
-time: 2022-08-23T11:26:33.8415455-07:00
-custom:
-  Author: panasenco
-  Issue: "5703"
-  PR: "5703"

.changes/unreleased/Fixes-20220903-155409.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: Removal of all .coverage files when using make clean command
-time: 2022-09-03T15:54:09.741554082+01:00
-custom:
-  Author: jared-rimmer
-  Issue: "5633"
-  PR: "5759"

.changes/unreleased/Fixes-20220909-092832.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: Remove temp files generated by unit tests
-time: 2022-09-09T09:28:32.590208+02:00
-custom:
-  Author: bbroeksema
-  Issue: "5631"
-  PR: "5749"

.changes/unreleased/Fixes-20220909-095627.yaml

@@ -1,7 +0,0 @@
-kind: Fixes
-body: Fix warnings as errors during tests
-time: 2022-09-09T09:56:27.90654-05:00
-custom:
-  Author: stu-k
-  Issue: "5424"
-  PR: "5800"

.changes/unreleased/Under the Hood-20220905-001749.yaml

@@ -1,7 +0,0 @@
-kind: Under the Hood
-body: Migrate integration test 014 but also fix the snapshot hard delete test's timezone logic and force all integration tests to run flags.set_from_args to force environment variables are accessible to all integration test threads.
-time: 2022-09-05T00:17:49.564534-07:00
-custom:
-  Author: versusfacit
-  Issue: "5760"
-  PR: "5760"

.changes/unreleased/Under the Hood-20220908-145644.yaml

@@ -1,7 +0,0 @@
-kind: Under the Hood
-body: Support dbt-metrics compilation by rebuilding flat_graph
-time: 2022-09-08T14:56:44.173322-04:00
-custom:
-  Author: gshank
-  Issue: "5525"
-  PR: "5786"

.changes/unreleased/Under the Hood-20220908-180731.yaml

@@ -1,8 +0,0 @@
-kind: Under the Hood
-body: Reworking the way we define the window attribute of metrics to match freshness
-  tests
-time: 2022-09-08T18:07:31.532608-05:00
-custom:
-  Author: callum-mcdata
-  Issue: "5722"
-  PR: "5793"

.changes/unreleased/Under the Hood-20220909-115220.yaml

@@ -1,7 +0,0 @@
-kind: Under the Hood
-body: Add PythonJobHelper base class in core and add more type checking
-time: 2022-09-09T11:52:20.419364-07:00
-custom:
-  Author: ChenyuLInx
-  Issue: "5802"
-  PR: "5802"

.changes/unreleased/Under the Hood-20220912-134000.yaml

@@ -1,7 +0,0 @@
-kind: Under the Hood
-body: Convert default selector tests to pytest
-time: 2022-09-12T13:40:00.625912-05:00
-custom:
-  Author: stu-k
-  Issue: "5728"
-  PR: "5820"

.changes/unreleased/Under the Hood-20220912-140035.yaml

@@ -1,7 +0,0 @@
-kind: Under the Hood
-body: The link did not go to the anchor directly, now it does
-time: 2022-09-12T14:00:35.899828+02:00
-custom:
-  Author: sdebruyn
-  Issue: "5813"
-  PR: "5814"

.changes/unreleased/Under the Hood-20220912-190341.yaml

@@ -1,7 +0,0 @@
-kind: Under the Hood
-body: remove key as reserved keyword from test_bool_or
-time: 2022-09-12T19:03:41.481601+02:00
-custom:
-  Author: sdebruyn
-  Issue: "5817"
-  PR: "5818"

.changie.yaml

@@ -7,26 +7,14 @@ versionExt: md
 versionFormat: '## dbt-core {{.Version}} - {{.Time.Format "January 02, 2006"}}'
 kindFormat: '### {{.Kind}}'
 changeFormat: '- {{.Body}} ([#{{.Custom.Issue}}](https://github.com/dbt-labs/dbt-core/issues/{{.Custom.Issue}}), [#{{.Custom.PR}}](https://github.com/dbt-labs/dbt-core/pull/{{.Custom.PR}}))'
-
 kinds:
-  - label: Breaking Changes
-  - label: Features
-  - label: Fixes
-  - label: Docs
-    changeFormat: '- {{.Body}} ([dbt-docs/#{{.Custom.Issue}}](https://github.com/dbt-labs/dbt-docs/issues/{{.Custom.Issue}}), [dbt-docs/#{{.Custom.PR}}](https://github.com/dbt-labs/dbt-docs/pull/{{.Custom.PR}}))'
-  - label: Under the Hood
-  - label: Dependencies
-    changeFormat: '- {{.Body}} ({{if ne .Custom.Issue ""}}[#{{.Custom.Issue}}](https://github.com/dbt-labs/dbt-core/issues/{{.Custom.Issue}}), {{end}}[#{{.Custom.PR}}](https://github.com/dbt-labs/dbt-core/pull/{{.Custom.PR}}))'
-  - label: Security
-    changeFormat: '- {{.Body}} ({{if ne .Custom.Issue ""}}[#{{.Custom.Issue}}](https://github.com/dbt-labs/dbt-core/issues/{{.Custom.Issue}}), {{end}}[#{{.Custom.PR}}](https://github.com/dbt-labs/dbt-core/pull/{{.Custom.PR}}))'
-
-newlines:
-  afterChangelogHeader: 1
-  afterKind: 1
-  afterChangelogVersion: 1
-  beforeKind: 1
-  endOfVersion: 1
-
+- label: Breaking Changes
+- label: Features
+- label: Fixes
+- label: Docs
+- label: Under the Hood
+- label: Dependencies
+- label: Security
 custom:
 - key: Author
   label: GitHub Username(s) (separated by a single space if multiple)
@@ -35,16 +23,15 @@ custom:
 - key: Issue
   label: GitHub Issue Number
   type: int
-  minInt: 1
+  minLength: 4
 - key: PR
   label: GitHub Pull Request Number
   type: int
-  minInt: 1
-
+  minLength: 4
 footerFormat: |
   {{- $contributorDict := dict }}
   {{- /* any names added to this list should be all lowercase for later matching purposes */}}
-  {{- $core_team := list "emmyoop" "nathaniel-may" "gshank" "leahwicz" "chenyulinx" "stu-k" "iknox-fa" "versusfacit" "mcknight-42" "jtcohen6" "dependabot[bot]" "snyk-bot" }}
+  {{- $core_team := list "emmyoop" "nathaniel-may" "gshank" "leahwicz" "chenyulinx" "stu-k" "iknox-fa" "versusfacit" "mcknight-42" "jtcohen6" "dependabot" }}
   {{- range $change := .Changes }}
     {{- $authorList := splitList " " $change.Custom.Author }}
     {{- /* loop through all authors for a PR */}}
@@ -52,20 +39,14 @@ footerFormat: |
       {{- $authorLower := lower $author }}
       {{- /* we only want to include non-core team contributors */}}
       {{- if not (has $authorLower $core_team)}}
-        {{- /* Docs kind link back to dbt-docs instead of dbt-core PRs */}}
-        {{- $prLink := $change.Kind }}
-        {{- if eq $change.Kind "Docs" }}
-          {{- $prLink = "[dbt-docs/#pr](https://github.com/dbt-labs/dbt-docs/pull/pr)" | replace "pr" $change.Custom.PR }}
-        {{- else }}
-          {{- $prLink = "[#pr](https://github.com/dbt-labs/dbt-core/pull/pr)" | replace "pr" $change.Custom.PR }}
-        {{- end }}
+        {{- $pr := $change.Custom.PR }}
         {{- /* check if this contributor has other PRs associated with them already */}}
         {{- if hasKey $contributorDict $author }}
           {{- $prList := get $contributorDict $author }}
-          {{- $prList = append $prList $prLink  }}
+          {{- $prList = append $prList $pr  }}
           {{- $contributorDict := set $contributorDict $author $prList }}
         {{- else }}
-          {{- $prList := list $prLink }}
+          {{- $prList := list $change.Custom.PR }}
           {{- $contributorDict := set $contributorDict $author $prList }}
         {{- end }}
       {{- end}}
@@ -75,6 +56,6 @@ footerFormat: |
   {{- if $contributorDict}}
   ### Contributors
   {{- range $k,$v := $contributorDict }}
-  - [@{{$k}}](https://github.com/{{$k}}) ({{ range $index, $element := $v }}{{if $index}}, {{end}}{{$element}}{{end}})
+  - [@{{$k}}](https://github.com/{{$k}}) ({{ range $index, $element := $v }}{{if $index}}, {{end}}[#{{$element}}](https://github.com/dbt-labs/dbt-core/pull/{{$element}}){{end}})
   {{- end }}
   {{- end }}

.github/CODEOWNERS

@@ -16,57 +16,25 @@
 # Changes to GitHub configurations including Actions
 /.github/ @leahwicz
 
-### LANGUAGE
-
 # Language core modules
-/core/dbt/config/               @dbt-labs/core-language
-/core/dbt/context/              @dbt-labs/core-language
-/core/dbt/contracts/            @dbt-labs/core-language
-/core/dbt/deps/                 @dbt-labs/core-language
-/core/dbt/events/               @dbt-labs/core-language  # structured logging
-/core/dbt/parser/               @dbt-labs/core-language
-
-# Language misc files
-/core/dbt/dataclass_schema.py   @dbt-labs/core-language
-/core/dbt/hooks.py              @dbt-labs/core-language
-/core/dbt/node_types.py         @dbt-labs/core-language
-/core/dbt/semver.py             @dbt-labs/core-language
-
-
-### EXECUTION
+/core/dbt/config/     @dbt-labs/core-language
+/core/dbt/context/    @dbt-labs/core-language
+/core/dbt/contracts/  @dbt-labs/core-language
+/core/dbt/deps/       @dbt-labs/core-language
+/core/dbt/parser/     @dbt-labs/core-language
 
 # Execution core modules
-/core/dbt/graph/                @dbt-labs/core-execution
-/core/dbt/task/                 @dbt-labs/core-execution
+/core/dbt/events/     @dbt-labs/core-execution @dbt-labs/core-language # eventually remove language but they have knowledge here now
+/core/dbt/graph/      @dbt-labs/core-execution
+/core/dbt/task/       @dbt-labs/core-execution
 
-# Execution misc files
-/core/dbt/compilation.py        @dbt-labs/core-execution
-/core/dbt/flags.py              @dbt-labs/core-execution
-/core/dbt/lib.py                @dbt-labs/core-execution
-/core/dbt/main.py               @dbt-labs/core-execution
-/core/dbt/profiler.py           @dbt-labs/core-execution
-/core/dbt/selected_resources.py @dbt-labs/core-execution
-/core/dbt/tracking.py           @dbt-labs/core-execution
-/core/dbt/version.py            @dbt-labs/core-execution
+# Adapter interface, scaffold, Postgres plugin
+/core/dbt/adapters    @dbt-labs/core-adapters
+/core/scripts/create_adapter_plugin.py    @dbt-labs/core-adapters
+/plugins/             @dbt-labs/core-adapters
 
-
-### ADAPTERS
-
-# Adapter interface ("base" + "sql" adapter defaults, cache)
-/core/dbt/adapters              @dbt-labs/core-adapters
-
-# Global project (default macros + materializations), starter project
-/core/dbt/include               @dbt-labs/core-adapters
-
-# Postgres plugin
-/plugins/                       @dbt-labs/core-adapters
-
-# Functional tests for adapter plugins
-/tests/adapter                  @dbt-labs/core-adapters
-
-### TESTS
-
-# Overlapping ownership for vast majority of unit + functional tests
+# Global project: default macros, including generic tests + materializations
+/core/dbt/include/global_project    @dbt-labs/core-execution @dbt-labs/core-adapters
 
 # Perf regression testing framework
 # This excludes the test project files itself since those aren't specific

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -9,33 +9,23 @@ body:
         Thanks for taking the time to fill out this bug report!
   - type: checkboxes
     attributes:
-      label: Is this a new bug in dbt-core?
-      description: >
-        In other words, is this an error, flaw, failure or fault in our software?
-
-        If this is a bug that broke existing functionality that used to work, please open a regression issue.
-        If this is a bug in an adapter plugin, please open an issue in the adapter's repository.
-        If this is a bug experienced while using dbt Cloud, please report to [support](mailto:support@getdbt.com).
-        If this is a request for help or troubleshooting code in your own dbt project, please join our [dbt Community Slack](https://www.getdbt.com/community/join-the-community/) or open a [Discussion question](https://github.com/dbt-labs/docs.getdbt.com/discussions).
-
-        Please search to see if an issue already exists for the bug you encountered.
+      label: Is there an existing issue for this?
+      description: Please search to see if an issue already exists for the bug you encountered.
       options:
-        - label: I believe this is a new bug in dbt-core
-          required: true
-        - label: I have searched the existing issues, and I could not find an existing issue for this bug
+        - label: I have searched the existing issues
           required: true
   - type: textarea
     attributes:
       label: Current Behavior
       description: A concise description of what you're experiencing.
     validations:
-      required: true
+      required: false
   - type: textarea
     attributes:
       label: Expected Behavior
       description: A concise description of what you expected to happen.
     validations:
-      required: true
+      required: false
   - type: textarea
     attributes:
       label: Steps To Reproduce
@@ -46,7 +36,7 @@ body:
         3. Run '...'
         4. See error...
     validations:
-      required: true
+      required: false
   - type: textarea
     id: logs
     attributes:
@@ -62,8 +52,8 @@ body:
       description: |
         examples:
           - **OS**: Ubuntu 20.04
-          - **Python**: 3.9.12 (`python3 --version`)
-          - **dbt-core**: 1.1.1 (`dbt --version`)
+          - **Python**: 3.7.2 (`python --version`)
+          - **dbt**: 0.21.0 (`dbt --version`)
       value: |
         - OS:
         - Python:
@@ -74,15 +64,13 @@ body:
   - type: dropdown
     id: database
     attributes:
-      label: Which database adapter are you using with dbt?
-      description: If the bug is specific to the database or adapter, please open the issue in that adapter's repository instead
+      label: What database are you using dbt with?
       multiple: true
       options:
         - postgres
         - redshift
         - snowflake
         - bigquery
-        - spark
         - other (mention it in "Additional Context")
     validations:
       required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -1,14 +1,4 @@
-blank_issues_enabled: false
 contact_links:
-  - name: Ask the community for help
-    url: https://github.com/dbt-labs/docs.getdbt.com/discussions
-    about: Need help troubleshooting? Check out our guide on how to ask
-  - name: Contact dbt Cloud support
-    url: mailto:support@getdbt.com
-    about: Are you using dbt Cloud? Contact our support team for help!
-  - name: Participate in Discussions
-    url: https://github.com/dbt-labs/dbt-core/discussions
-    about: Do you have a Big Idea for dbt? Read open discussions, or start a new one
   - name: Create an issue for dbt-redshift
     url: https://github.com/dbt-labs/dbt-redshift/issues/new/choose
     about: Report a bug or request a feature for dbt-redshift
@@ -18,6 +8,9 @@ contact_links:
   - name: Create an issue for dbt-snowflake
     url: https://github.com/dbt-labs/dbt-snowflake/issues/new/choose
     about: Report a bug or request a feature for dbt-snowflake
-  - name: Create an issue for dbt-spark
-    url: https://github.com/dbt-labs/dbt-spark/issues/new/choose
-    about: Report a bug or request a feature for dbt-spark
+  - name: Ask a question or get support
+    url: https://docs.getdbt.com/docs/guides/getting-help
+    about: Ask a question or request support
+  - name: Questions on Stack Overflow
+    url: https://stackoverflow.com/questions/tagged/dbt
+    about: Look at questions/answers at Stack Overflow

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -1,5 +1,5 @@
 name: ✨ Feature
-description: Propose a straightforward extension of dbt functionality
+description: Suggest an idea for dbt
 title: "[Feature] <title>"
 labels: ["enhancement", "triage"]
 body:
@@ -9,24 +9,18 @@ body:
         Thanks for taking the time to fill out this feature request!
   - type: checkboxes
     attributes:
-      label: Is this your first time submitting a feature request?
-      description: >
-        We want to make sure that features are distinct and discoverable,
-        so that other members of the community can find them and offer their thoughts.
-
-        Issues are the right place to request straightforward extensions of existing dbt functionality.
-        For "big ideas" about future capabilities of dbt, we ask that you open a
-        [discussion](https://github.com/dbt-labs/dbt-core/discussions) in the "Ideas" category instead.
+      label: Is there an existing feature request for this?
+      description: Please search to see if an issue already exists for the feature you would like.
+      options:
+        - label: I have searched the existing issues
+          required: true
+      label: Is this your first time opening an issue?
       options:
         - label: I have read the [expectations for open source contributors](https://docs.getdbt.com/docs/contributing/oss-expectations)
           required: true
-        - label: I have searched the existing issues, and I could not find an existing issue for this feature
-          required: true
-        - label: I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion
-          required: true
   - type: textarea
     attributes:
-      label: Describe the feature
+      label: Describe the Feature
       description: A clear and concise description of what you want to happen.
     validations:
       required: true

.github/ISSUE_TEMPLATE/regression-report.yml

@@ -1,93 +0,0 @@
-name: ☣️ Regression
-description: Report a regression you've observed in a newer version of dbt
-title: "[Regression] <title>"
-labels: ["bug", "regression", "triage"]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for taking the time to fill out this regression report!
-  - type: checkboxes
-    attributes:
-      label: Is this a regression in a recent version of dbt-core?
-      description: >
-        A regression is when documented functionality works as expected in an older version of dbt-core,
-        and no longer works after upgrading to a newer version of dbt-core
-      options:
-        - label: I believe this is a regression in dbt-core functionality
-          required: true
-        - label: I have searched the existing issues, and I could not find an existing issue for this regression
-          required: true
-  - type: textarea
-    attributes:
-      label: Current Behavior
-      description: A concise description of what you're experiencing.
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: Expected/Previous Behavior
-      description: A concise description of what you expected to happen.
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: Steps To Reproduce
-      description: Steps to reproduce the behavior.
-      placeholder: |
-        1. In this environment...
-        2. With this config...
-        3. Run '...'
-        4. See error...
-    validations:
-      required: true
-  - type: textarea
-    id: logs
-    attributes:
-      label: Relevant log output
-      description: |
-        If applicable, log output to help explain your problem.
-      render: shell
-    validations:
-      required: false
-  - type: textarea
-    attributes:
-      label: Environment
-      description: |
-        examples:
-          - **OS**: Ubuntu 20.04
-          - **Python**: 3.9.12 (`python3 --version`)
-          - **dbt-core (working version)**: 1.1.1 (`dbt --version`)
-          - **dbt-core (regression version)**: 1.2.0 (`dbt --version`)
-      value: |
-        - OS:
-        - Python:
-        - dbt (working version):
-        - dbt (regression version):
-      render: markdown
-    validations:
-      required: true
-  - type: dropdown
-    id: database
-    attributes:
-      label: Which database adapter are you using with dbt?
-      description: If the regression is specific to the database or adapter, please open the issue in that adapter's repository instead
-      multiple: true
-      options:
-        - postgres
-        - redshift
-        - snowflake
-        - bigquery
-        - spark
-        - other (mention it in "Additional Context")
-    validations:
-      required: false
-  - type: textarea
-    attributes:
-      label: Additional Context
-      description: |
-        Links? References? Anything that will give us more context about the issue you are encountering!
-
-        Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
-    validations:
-      required: false

.github/_README.md

@@ -1,216 +0,0 @@
-<!-- GitHub will publish this readme on the main repo page if the name is `README.md` so we've added the leading underscore to prevent this -->
-<!-- Do not rename this file `README.md` -->
-<!-- See https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes -->
-
-## What are GitHub Actions?
-
-GitHub Actions are used for many different purposes.  We use them to run tests in CI, validate PRs are in an expected state, and automate processes.
-
-- [Overview of GitHub Actions](https://docs.github.com/en/actions/learn-github-actions/understanding-github-actions)
-- [What's a workflow?](https://docs.github.com/en/actions/using-workflows/about-workflows)
-- [GitHub Actions guides](https://docs.github.com/en/actions/guides)
-
-___
-
-## Where do actions and workflows live
-
-We try to maintain actions that are shared across repositories in a single place so that necesary changes can be made in a single place.
-
-[dbt-labs/actions](https://github.com/dbt-labs/actions/) is the central repository of actions and workflows we use across repositories.
-
-GitHub Actions also live locally within a repository.  The workflows can be found at `.github/workflows` from the root of the repository.  These should be specific to that code base.
-
-Note: We are actively moving actions into the central Action repository so there is currently some duplication across repositories.
-
-___
-
-## Basics of Using Actions
-
-### Viewing Output
-
-- View the detailed action output for your PR in the **Checks** tab of the PR.  This only shows the most recent run.  You can also view high level **Checks** output at the bottom on the PR.
-
-- View _all_ action output for a repository from the [**Actions**](https://github.com/dbt-labs/dbt-core/actions) tab.  Workflow results last 1 year.  Artifacts last 90 days, unless specified otherwise in individual workflows.
-
-  This view often shows what seem like duplicates of the same workflow.  This occurs when files are renamed but the workflow name has not changed.  These are in fact _not_ duplicates.
-
-  You can see the branch the workflow runs from in this view.  It is listed in the table between the workflow name and the time/duration of the run.  When blank, the workflow is running in the context of the  `main` branch.
-
-### How to view what workflow file is being referenced from a run
-
-- When viewing the output of a specific workflow run, click the 3 dots at the top right of the display.  There will be an option to `View workflow file`.
-
-### How to manually run a workflow
-
-- If a workflow has the `on: workflow_dispatch` trigger, it can be manually triggered
-- From the [**Actions**](https://github.com/dbt-labs/dbt-core/actions) tab, find the workflow you want to run, select it and fill in any inputs requied.  That's it!
-
-### How to re-run jobs
-
-- Some actions cannot be rerun in the GitHub UI.  Namely the snyk checks and the cla check.  Snyk checks are rerun by closing and reopening the PR.  You can retrigger the cla check by commenting on the PR with `@cla-bot check`
-
-___
-
-## General Standards
-
-### Permissions
-- By default, workflows have read permissions in the repository for the contents scope only when no permissions are explicitly set.
-- It is best practice to always define the permissions explicitly.  This will allow actions to continue to work when the default permissions on the repository are changed.  It also allows explicit grants of the least permissions possible.
-- There are a lot of permissions available.  [Read up on them](https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs) if you're unsure what to use.
-
-```yaml
-permissions:
-  contents: read
-  pull-requests: write
-```
-    
-### Secrets
-- When to use a [Personal Access Token (PAT)](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) vs the [GITHUB_TOKEN](https://docs.github.com/en/actions/security-guides/automatic-token-authentication) generated for the action?
-
-    The `GITHUB_TOKEN` is used by default.  In most cases it is sufficient for what you need.
-    
-    If you expect the workflow to result in a commit to that should retrigger workflows, you will need to use a Personal Access Token for the bot to commit the file. When using the GITHUB_TOKEN, the resulting commit will not trigger another GitHub Actions Workflow run. This is due to limitations set by GitHub. See [the docs](https://docs.github.com/en/actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow) for a more detailed explanation.
-
-    For example, we must use a PAT in our workflow to commit a new changelog yaml file for bot PRs.  Once the file has been committed to the branch, it should retrigger the check to validate that a changelog exists on the PR.  Otherwise, it would stay in a failed state since the check would never retrigger.
-
-### Triggers
-You can configure your workflows to run when specific activity on GitHub happens, at a scheduled time, or when an event outside of GitHub occurs.  Read more details in the [GitHub docs](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows).
-
-These triggers are under the `on` key of the workflow and more than one can be listed.
-
-```yaml
-on:
-  push:
-    branches:
-      - "main"
-      - "*.latest"
-      - "releases/*"
-  pull_request:
-    # catch when the PR is opened with the label or when the label is added
-    types: [opened, labeled]
-  workflow_dispatch:
-```
-
-Some triggers of note that we use:
-
-- `push` - Runs your workflow when you push a commit or tag.
-- `pull_request` - Runs your workflow when activity on a pull request in the workflow's repository occurs.  Takes in a list of activity types (opened, labeled, etc) if appropriate.
-- `pull_request_target` - Same as `pull_request` but runs in the context of the PR target branch.
-- `workflow_call` - used with reusable workflows.  Triggered by another workflow calling it.
-- `workflow_dispatch` - Gives the ability to manually trigger a workflow from the GitHub API, GitHub CLI, or GitHub browser interface.
-
-
-### Basic Formatting
-- Add a description of what your workflow does at the top in this format
-
-  ```
-  # **what?**
-  # Describe what the action does.  
-
-  # **why?**
-  # Why does this action exist?
-
-  # **when?**
-  # How/when will it be triggered?
-  ```
-
-- Leave blank lines between steps and jobs
-
-  ```yaml
-  jobs:
-    dependency_changelog:
-      runs-on: ubuntu-latest
-
-      steps:
-      - name: Get File Name Timestamp
-        id: filename_time
-        uses: nanzm/get-time-action@v1.1
-        with:
-          format: 'YYYYMMDD-HHmmss'
-
-      - name: Get File Content Timestamp
-        id: file_content_time
-        uses: nanzm/get-time-action@v1.1
-        with:
-          format: 'YYYY-MM-DDTHH:mm:ss.000000-05:00'
-
-      - name: Generate Filepath
-        id: fp
-        run: |
-          FILEPATH=.changes/unreleased/Dependencies-${{ steps.filename_time.outputs.time }}.yaml
-          echo "::set-output name=FILEPATH::$FILEPATH"
-  ```
-
-- Print out all variables you will reference as the first step of a job.  This allows for easier debugging.  The first job should log all inputs.  Subsequent jobs should reference outputs of other jobs, if present.
-
-  When possible, generate variables at the top of your workflow in a single place to reference later.  This is not always strictly possible since you may generate a value to be used later mid-workflow.
-
-  Be sure to use quotes around these logs so special characters are not interpreted.
-
-  ```yaml
-  job1:
-    - name: "[DEBUG] Print Variables"
-      run: |
-        echo "all variables defined as inputs"
-        echo "The last commit sha in the release: ${{ inputs.sha }}"
-        echo "The release version number:         ${{ inputs.version_number }}"
-        echo "The changelog_path:                 ${{ inputs.changelog_path }}"
-        echo "The build_script_path:              ${{ inputs.build_script_path }}"
-        echo "The s3_bucket_name:                 ${{ inputs.s3_bucket_name }}"
-        echo "The package_test_command:           ${{ inputs.package_test_command }}"
-      
-    # collect all the variables that need to be used in subsequent jobs
-    - name: Set Variables
-      id: variables
-      run: |
-        echo "::set-output name=important_path::'performance/runner/Cargo.toml'"
-        echo "::set-output name=release_id::${{github.event.inputs.release_id}}"
-        echo "::set-output name=open_prs::${{github.event.inputs.open_prs}}"
-
-  job2:
-    needs: [job1]
-      - name: "[DEBUG] Print Variables"
-      run: |
-        echo "all variables defined in job1 > Set Variables > outputs"
-        echo "important_path: ${{ needs.job1.outputs.important_path }}"
-        echo "release_id:     ${{ needs.job1.outputs.release_id }}"
-        echo "open_prs:       ${{ needs.job1.outputs.open_prs }}"
-  ```
-
-- When it's not obvious what something does, add a comment!
-
-___
-
-## Tips
-
-### Context
-- The [GitHub CLI](https://cli.github.com/) is available in the default runners
-- Actions run in your context.  ie, using an action from the marketplace that uses the GITHUB_TOKEN uses the GITHUB_TOKEN generated by your workflow run.
-
-### Actions from the Marketplace
-- Don’t use external actions for things that can easily be accomplished manually.
-- Always read through what an external action does before using it!  Often an action in the GitHub Actions Marketplace can be replaced with a few lines in bash.  This is much more maintainable (and won’t change under us) and clear as to what’s actually happening.  It also prevents any
-- Pin actions _we don't control_ to tags. 
-
-### Connecting to AWS
-- Authenticate with the aws managed workflow
-
-  ```yaml
-  - name: Configure AWS credentials from Test account
-    uses: aws-actions/configure-aws-credentials@v1
-    with:
-      aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
-      aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
-      aws-region: us-east-1
-  ```
-
-- Then access with the aws command that comes installed on the action runner machines
-
-  ```yaml
-  - name: Copy Artifacts from S3 via CLI
-    run: aws s3 cp ${{ env.s3_bucket }} . --recursive 
-  ```
-
-### Testing
-
-- Depending on what your action does, you may be able to use [`act`](https://github.com/nektos/act) to test the action locally.  Some features of GitHub Actions do not work with `act`, among those are reusable workflows.  If you can't use `act`, you'll have to push your changes up before being able to test.  This can be slow.

.github/pull_request_template.md

@@ -20,4 +20,4 @@ resolves #
 - [ ] I have run this code in development and it appears to resolve the stated issue
 - [ ] This PR includes tests, or tests are not required/relevant for this PR
 - [ ] I have [opened an issue to add/update docs](https://github.com/dbt-labs/docs.getdbt.com/issues/new/choose), or docs changes are not required/relevant for this PR
-- [ ] I have run `changie new` to [create a changelog entry](https://github.com/dbt-labs/dbt-core/blob/main/CONTRIBUTING.md#adding-a-changelog-entry)
+- [ ] I have run `changie new` to [create a changelog entry](https://github.com/dbt-labs/dbt-core/blob/main/CONTRIBUTING.md#Adding-CHANGELOG-Entry)

.github/workflows/bot-changelog.yml

@@ -1,61 +0,0 @@
-# **what?**
-# When bots create a PR, this action will add a corresponding changie yaml file to that
-# PR when a specific label is added.
-#
-# The file is created off a template:
-#
-# kind: <per action matrix>
-# body: <PR title>
-# time: <current timestamp>
-# custom:
-#   Author: <PR User Login (generally the bot)>
-#   Issue: 4904
-#   PR: <PR number>
-#
-# **why?**
-# Automate changelog generation for more visability with automated bot PRs.
-#
-# **when?**
-# Once a PR is created, label should be added to PR before or after creation. You can also
-#  manually trigger this by adding the appropriate label at any time.
-#
-# **how to add another bot?**
-# Add the label and changie kind to the include matrix.  That's it!
-#
-
-name: Bot Changelog
-
-on:
-  pull_request:
-    # catch when the PR is opened with the label or when the label is added
-    types: [labeled]
-
-permissions:
-  contents: write
-  pull-requests: read
-
-jobs:
-  generate_changelog:
-    strategy:
-      matrix:
-        include:
-          - label: "dependencies"
-            changie_kind: "Dependency"
-          - label: "snyk"
-            changie_kind: "Security"
-    runs-on: ubuntu-latest
-
-    steps:
-
-    - name: Create and commit changelog on bot PR
-      if: ${{ contains(github.event.pull_request.labels.*.name, matrix.label) }}
-      id: bot_changelog
-      uses: emmyoop/changie_bot@v1.0.1
-      with:
-        GITHUB_TOKEN: ${{ secrets.FISHTOWN_BOT_PAT }}
-        commit_author_name: "Github Build Bot"
-        commit_author_email: "<buildbot@fishtownanalytics.com>"
-        commit_message: "Add automated changelog yaml from template for bot PR"
-        changie_kind: ${{ matrix.changie_kind }}
-        label: ${{ matrix.label }}
-        custom_changelog_string: "custom:\n  Author: ${{ github.event.pull_request.user.login }}\n  Issue: 4904\n  PR: ${{ github.event.pull_request.number }}"

.github/workflows/changelog-check.yml

@@ -0,0 +1,78 @@
+# **what?**
+# Checks that a file has been committed under the /.changes directory
+# as a new CHANGELOG entry.  Cannot check for a specific filename as
+# it is dynamically generated by change type and timestamp.
+# This workflow should not require any secrets since it runs for PRs
+# from forked repos.
+# By default, secrets are not passed to workflows running from
+# a forked repo.
+
+# **why?**
+# Ensure code change gets reflected in the CHANGELOG.
+
+# **when?**
+# This will run for all PRs going into main and *.latest.  It will
+# run when they are opened, reopened, when any label is added or removed
+# and when new code is pushed to the branch.  The action will then get
+# skipped if the 'Skip Changelog' label is present is any of the labels.
+
+name: Check Changelog Entry
+
+on:
+  pull_request:
+    types: [opened, reopened, labeled, unlabeled, synchronize]
+  workflow_dispatch:
+
+defaults:
+  run:
+    shell: bash
+
+permissions:
+  contents: read
+  pull-requests: write
+
+env:
+  changelog_comment: 'Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see [the contributing guide](https://github.com/dbt-labs/dbt-core/blob/main/CONTRIBUTING.md#adding-changelog-entry).'
+
+jobs:
+  changelog:
+    name: changelog
+    if: "!contains(github.event.pull_request.labels.*.name, 'Skip Changelog')"
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Check if changelog file was added
+        # https://github.com/marketplace/actions/paths-changes-filter
+        # For each filter, it sets output variable named by the filter to the text:
+        #  'true' - if any of changed files matches any of filter rules
+        #  'false' - if none of changed files matches any of filter rules
+        # also, returns:
+        #  `changes` - JSON array with names of all filters matching any of the changed files
+        uses: dorny/paths-filter@v2
+        id: filter
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          filters: |
+            changelog:
+              - added: '.changes/unreleased/**.yaml'
+      - name: Check if comment already exists
+        uses: peter-evans/find-comment@v1
+        id: changelog_comment
+        with:
+          issue-number: ${{ github.event.pull_request.number }}
+          comment-author: 'github-actions[bot]'
+          body-includes: ${{ env.changelog_comment }}
+      - name: Create PR comment if changelog entry is missing, required, and does not exist
+        if: |
+          steps.filter.outputs.changelog == 'false' &&
+          steps.changelog_comment.outputs.comment-body == ''
+        uses: peter-evans/create-or-update-comment@v1
+        with:
+          issue-number: ${{ github.event.pull_request.number }}
+          body: ${{ env.changelog_comment }}
+      - name: Fail job if changelog entry is missing and required
+        if: steps.filter.outputs.changelog == 'false'
+        uses: actions/github-script@v6
+        with:
+          script: core.setFailed('Changelog entry required to merge.')

.github/workflows/changelog-existence.yml

@@ -1,40 +0,0 @@
-# **what?**
-# Checks that a file has been committed under the /.changes directory
-# as a new CHANGELOG entry.  Cannot check for a specific filename as
-# it is dynamically generated by change type and timestamp.
-# This workflow should not require any secrets since it runs for PRs
-# from forked repos.
-# By default, secrets are not passed to workflows running from
-# a forked repo.
-
-# **why?**
-# Ensure code change gets reflected in the CHANGELOG.
-
-# **when?**
-# This will run for all PRs going into main and *.latest.  It will
-# run when they are opened, reopened, when any label is added or removed
-# and when new code is pushed to the branch.  The action will then get
-# skipped if the 'Skip Changelog' label is present is any of the labels.
-
-name: Check Changelog Entry
-
-on:
-  pull_request:
-    types: [opened, reopened, labeled, unlabeled, synchronize]
-  workflow_dispatch:
-
-defaults:
-  run:
-    shell: bash
-
-permissions:
-  contents: read
-  pull-requests: write
-
-jobs:
-  changelog:
-    uses: dbt-labs/actions/.github/workflows/changelog-existence.yml@main
-    with:
-      changelog_comment: 'Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see [the contributing guide](https://github.com/dbt-labs/dbt-core/blob/main/CONTRIBUTING.md#adding-changelog-entry).'
-      skip_label: 'Skip Changelog'
-    secrets: inherit

.github/workflows/dependency-changelog.yml

@@ -0,0 +1,114 @@
+# **what?**
+# When dependabot create a PR, it always adds the `dependencies` label. This
+# action will add a corresponding changie yaml file to that PR when that label is added.
+# The file is created off a template:
+#
+# kind: Dependencies
+# body: <PR title>
+# time: <current timestamp>
+# custom:
+#   Author: dependabot
+#   Issue: 4904
+#   PR: <PR number>
+#
+# **why?**
+# Automate changelog generation for more visability with automated dependency updates via dependabot.
+
+# **when?**
+# Once a PR is created and it has been correctly labeled with `dependencies`.  The intended use
+# is for the PRs created by dependabot.  You can also manually trigger this by adding the
+# `dependencies` label at any time.
+
+name: Dependency Changelog
+
+on:
+  pull_request:
+    # catch when the PR is opened with the label or when the label is added
+    types: [opened, labeled]
+
+permissions:
+  contents: write
+  pull-requests: read
+
+jobs:
+  dependency_changelog:
+    if: "contains(github.event.pull_request.labels.*.name, 'dependencies')"
+    runs-on: ubuntu-latest
+
+    steps:
+    # timestamp changes the order the changelog entries are listed in the final Changelog.md file.  Precision is not
+    # important here.
+    # The timestamp on the filename and the timestamp in the contents of the file have different expected formats.
+    - name: Get File Name Timestamp
+      id: filename_time
+      uses: nanzm/get-time-action@v1.1
+      with:
+        format: 'YYYYMMDD-HHmmss'
+
+    - name: Get File Content Timestamp
+      id: file_content_time
+      uses: nanzm/get-time-action@v1.1
+      with:
+        format: 'YYYY-MM-DDTHH:mm:ss.000000-05:00'
+
+    # changie expects files to be named in a specific pattern.
+    - name: Generate Filepath
+      id: fp
+      run: |
+        FILEPATH=.changes/unreleased/Dependencies-${{ steps.filename_time.outputs.time }}.yaml
+        echo "::set-output name=FILEPATH::$FILEPATH"
+
+    - name: Check if changelog file exists already
+      # if there's already a changelog entry, don't add another one!
+      # https://github.com/marketplace/actions/paths-changes-filter
+      # For each filter, it sets output variable named by the filter to the text:
+      #  'true' - if any of changed files matches any of filter rules
+      #  'false' - if none of changed files matches any of filter rules
+      # also, returns:
+      #  `changes` - JSON array with names of all filters matching any of the changed files
+      uses: dorny/paths-filter@v2
+      id: changelog_check
+      with:
+        token: ${{ secrets.GITHUB_TOKEN }}
+        filters: |
+          exists:
+            - added: '.changes/unreleased/**.yaml'
+
+    - name: Checkout Branch
+      if: steps.changelog_check.outputs.exists == 'false'
+      uses: actions/checkout@v2
+      with:
+        # specifying the ref avoids checking out the repository in a detached state
+        ref: ${{ github.event.pull_request.head.ref }}
+        # If this is not set to false, Git push is performed with github.token and not the token
+        # configured using the env: GITHUB_TOKEN in commit step
+        persist-credentials: false
+
+    - name: Create file from template
+      if: steps.changelog_check.outputs.exists == 'false'
+      run: |
+        echo kind: Dependencies > "${{ steps.fp.outputs.FILEPATH }}"
+        echo 'body: "${{ github.event.pull_request.title }}"' >> "${{ steps.fp.outputs.FILEPATH }}"
+        echo time: "${{ steps.file_content_time.outputs.time }}" >> "${{ steps.fp.outputs.FILEPATH }}"
+        echo custom: >> "${{ steps.fp.outputs.FILEPATH }}"
+        echo '  Author: ${{ github.event.pull_request.user.login }}' >> "${{ steps.fp.outputs.FILEPATH }}"
+        echo '  Issue: "4904"' >> "${{ steps.fp.outputs.FILEPATH }}"  # github.event.pull_request.issue for auto id?
+        echo '  PR: "${{ github.event.pull_request.number }}"' >> "${{ steps.fp.outputs.FILEPATH }}"
+
+    - name: Commit Changelog File
+      if: steps.changelog_check.outputs.exists == 'false'
+      uses: gr2m/create-or-update-pull-request-action@v1
+      env:
+        # When using the GITHUB_TOKEN, the resulting commit will not trigger another GitHub Actions
+        # Workflow run. This is due to limitations set by GitHub.
+        # See: https://docs.github.com/en/actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow
+        # When you use the repository's GITHUB_TOKEN to perform tasks on behalf of the GitHub Actions
+        # app, events triggered by the GITHUB_TOKEN will not create a new workflow run. This prevents
+        # you from accidentally creating recursive workflow runs. To get around this, use a Personal
+        # Access Token to commit changes.
+        GITHUB_TOKEN: ${{ secrets.FISHTOWN_BOT_PAT }}
+      with:
+        branch: ${{ github.event.pull_request.head.ref }}
+        # author expected in the format "Lorem J. Ipsum <lorem@example.com>"
+        author: "Github Build Bot <buildbot@fishtownanalytics.com>"
+        commit-message: "Add automated changelog yaml from template"

.github/workflows/release-branch-tests.yml

@@ -39,7 +39,7 @@ jobs:
       max-parallel: 1
       fail-fast: false
       matrix:
-        branch: [1.0.latest, 1.1.latest, 1.2.latest, main]
+        branch: [1.0.latest, 1.1.latest, main]
 
     steps:
     - name: Call CI workflow for ${{ matrix.branch }} branch

.github/workflows/version-bump.yml

@@ -1,15 +1,18 @@
 # **what?**
-# This workflow will take the new version number to bump to. With that
+# This workflow will take a version number and a dry run flag. With that
 # it will run versionbump to update the version number everywhere in the
-# code base and then run changie to create the corresponding changelog.
-# A PR will be created with the changes that can be reviewed before committing.
+# code base and then generate an update Docker requirements file. If this
+# is a dry run, a draft PR will open with the changes. If this isn't a dry
+# run, the changes will be committed to the branch this is run on.
 
 # **why?**
 # This is to aid in releasing dbt and making sure we have updated
-# the version in all places and generated the changelog.
+# the versions and Docker requirements in all places.
 
 # **when?**
-# This is triggered manually
+# This is triggered either manually OR
+# from the repository_dispatch event "version-bump" which is sent from
+# the dbt-release repo Action
 
 name: Version Bump
 
@@ -17,21 +20,35 @@ on:
   workflow_dispatch:
     inputs:
       version_number:
-       description: 'The version number to bump to (ex. 1.2.0, 1.3.0b1)'
+       description: 'The version number to bump to'
        required: true
+      is_dry_run:
+       description: 'Creates a draft PR to allow testing instead of committing to a branch'
+       required: true
+       default: 'true'
+  repository_dispatch:
+    types: [version-bump]
 
 jobs:
   bump:
     runs-on: ubuntu-latest
     steps:
-      - name: "[DEBUG] Print Variables"
-        run: |
-          echo "all variables defined as inputs"
-          echo The version_number: ${{ github.event.inputs.version_number }}
-
       - name: Check out the repository
         uses: actions/checkout@v2
 
+      - name: Set version and dry run values
+        id: variables
+        env:
+          VERSION_NUMBER: "${{ github.event.client_payload.version_number == '' && github.event.inputs.version_number || github.event.client_payload.version_number }}"
+          IS_DRY_RUN: "${{ github.event.client_payload.is_dry_run == '' && github.event.inputs.is_dry_run || github.event.client_payload.is_dry_run }}"
+        run: |
+          echo Repository dispatch event version: ${{ github.event.client_payload.version_number }}
+          echo Repository dispatch event dry run: ${{ github.event.client_payload.is_dry_run }}
+          echo Workflow dispatch event version: ${{ github.event.inputs.version_number }}
+          echo Workflow dispatch event dry run: ${{ github.event.inputs.is_dry_run }}
+          echo ::set-output name=VERSION_NUMBER::$VERSION_NUMBER
+          echo ::set-output name=IS_DRY_RUN::$IS_DRY_RUN
+
       - uses: actions/setup-python@v2
         with:
           python-version: "3.8"
@@ -42,66 +59,53 @@ jobs:
           source env/bin/activate
           pip install --upgrade pip
 
-      - name: Audit Version and Parse Into Parts
-        id: semver
-        uses: dbt-labs/actions/parse-semver@v1
-        with:
-          version: ${{ github.event.inputs.version_number }}
-
-      - name: Set branch value
-        id: variables
-        run: |
-          echo "::set-output name=BRANCH_NAME::prep-release/${{ github.event.inputs.version_number }}_$GITHUB_RUN_ID"
-
       - name: Create PR branch
+        if: ${{ steps.variables.outputs.IS_DRY_RUN == 'true' }}
         run: |
-          git checkout -b ${{ steps.variables.outputs.BRANCH_NAME }}
-          git push origin ${{ steps.variables.outputs.BRANCH_NAME }}
-          git branch --set-upstream-to=origin/${{ steps.variables.outputs.BRANCH_NAME }} ${{ steps.variables.outputs.BRANCH_NAME }}
+          git checkout -b bumping-version/${{steps.variables.outputs.VERSION_NUMBER}}_$GITHUB_RUN_ID
+          git push origin bumping-version/${{steps.variables.outputs.VERSION_NUMBER}}_$GITHUB_RUN_ID
+          git branch --set-upstream-to=origin/bumping-version/${{steps.variables.outputs.VERSION_NUMBER}}_$GITHUB_RUN_ID bumping-version/${{steps.variables.outputs.VERSION_NUMBER}}_$GITHUB_RUN_ID
+
+      # - name: Generate Docker requirements
+      #  run: |
+      #    source env/bin/activate
+      #    pip install -r requirements.txt
+      #    pip freeze -l > docker/requirements/requirements.txt
+      #    git status
 
       - name: Bump version
         run: |
           source env/bin/activate
           pip install -r dev-requirements.txt
-          env/bin/bumpversion --allow-dirty --new-version ${{ github.event.inputs.version_number }} major
+          env/bin/bumpversion --allow-dirty --new-version ${{steps.variables.outputs.VERSION_NUMBER}} major
           git status
 
-      # this step will fail on whitespace errors but also correct them
-      - name: Format bumpversion file
-        continue-on-error: true
-        run: |
-          brew install pre-commit
-          pre-commit run trailing-whitespace --files .bumpversion.cfg
-          git status
-
-      - name: Run changie
-        run: |
-          brew tap miniscruff/changie https://github.com/miniscruff/changie
-          brew install changie
-          if [[ ${{ steps.semver.outputs.is-pre-release }} -eq 1 ]]
-          then
-            changie batch ${{ steps.semver.outputs.base-version }}  --move-dir '${{ steps.semver.outputs.base-version }}' --prerelease '${{ steps.semver.outputs.pre-release }}'
-          else
-            changie batch ${{ steps.semver.outputs.base-version }}  --include '${{ steps.semver.outputs.base-version }}' --remove-prereleases
-          fi
-          changie merge
-          git status
-
-      - name: Commit version bump to branch
+      - name: Commit version bump directly
         uses: EndBug/add-and-commit@v7
+        if: ${{ steps.variables.outputs.IS_DRY_RUN == 'false' }}
         with:
           author_name: 'Github Build Bot'
           author_email: 'buildbot@fishtownanalytics.com'
-          message: 'Bumping version to ${{ github.event.inputs.version_number }} and generate CHANGELOG'
-          branch: '${{ steps.variables.outputs.BRANCH_NAME }}'
-          push: 'origin origin/${{ steps.variables.outputs.BRANCH_NAME }}'
+          message: 'Bumping version to ${{steps.variables.outputs.VERSION_NUMBER}}'
+
+      - name: Commit version bump to branch
+        uses: EndBug/add-and-commit@v7
+        if: ${{ steps.variables.outputs.IS_DRY_RUN == 'true' }}
+        with:
+          author_name: 'Github Build Bot'
+          author_email: 'buildbot@fishtownanalytics.com'
+          message: 'Bumping version to ${{steps.variables.outputs.VERSION_NUMBER}}'
+          branch: 'bumping-version/${{steps.variables.outputs.VERSION_NUMBER}}_${{GITHUB.RUN_ID}}'
+          push: 'origin origin/bumping-version/${{steps.variables.outputs.VERSION_NUMBER}}_${{GITHUB.RUN_ID}}'
 
       - name: Create Pull Request
         uses: peter-evans/create-pull-request@v3
+        if: ${{ steps.variables.outputs.IS_DRY_RUN == 'true' }}
         with:
           author: 'Github Build Bot <buildbot@fishtownanalytics.com>'
+          draft: true
           base: ${{github.ref}}
-          title: 'Bumping version to ${{ github.event.inputs.version_number }} and generate changelog'
-          branch: '${{ steps.variables.outputs.BRANCH_NAME }}'
+          title: 'Bumping version to ${{steps.variables.outputs.VERSION_NUMBER}}'
+          branch: 'bumping-version/${{steps.variables.outputs.VERSION_NUMBER}}_${{GITHUB.RUN_ID}}'
           labels: |
             Skip Changelog

.gitignore

@@ -95,7 +95,3 @@ venv/
 
 # vscode
 .vscode/
-
-# poetry
-pyproject.toml
-poetry.lock

.pre-commit-config.yaml

@@ -6,7 +6,7 @@ exclude: ^test/
 
 # Force all unspecified python hooks to run python 3.8
 default_language_version:
-  python: python3
+  python: python3.8
 
 repos:
 - repo: https://github.com/pre-commit/pre-commit-hooks

CHANGELOG.md

@@ -5,95 +5,6 @@
 - "Breaking changes" listed under a version may require action from end users or external maintainers when upgrading to that version.
 - Do not edit this file directly. This file is auto-generated using [changie](https://github.com/miniscruff/changie). For details on how to document a change, see [the contributing guide](https://github.com/dbt-labs/dbt-core/blob/main/CONTRIBUTING.md#adding-changelog-entry)
 
-## dbt-core 1.3.0-b2 - August 29, 2022
-
-### Features
-
-- Add `--defer` flag to dbt compile & dbt docs generate ([#4110](https://github.com/dbt-labs/dbt-core/issues/4110), [#4514](https://github.com/dbt-labs/dbt-core/pull/4514))
-- use MethodName.File when value ends with .csv ([#5578](https://github.com/dbt-labs/dbt-core/issues/5578), [#5581](https://github.com/dbt-labs/dbt-core/pull/5581))
-- Make `docs` configurable in `dbt_project.yml` and add a `node_color` attribute to change the color of nodes in the DAG ([#5333](https://github.com/dbt-labs/dbt-core/issues/5333), [#5397](https://github.com/dbt-labs/dbt-core/pull/5397))
-- Adding ResolvedMetricReference helper functions and tests ([#5567](https://github.com/dbt-labs/dbt-core/issues/5567), [#5607](https://github.com/dbt-labs/dbt-core/pull/5607))
-- Check dbt-core version requirements when installing Hub packages ([#5648](https://github.com/dbt-labs/dbt-core/issues/5648), [#5651](https://github.com/dbt-labs/dbt-core/pull/5651))
-
-### Fixes
-
-- Remove the default 256 characters limit on postgres character varying type when no limitation is set ([#5238](https://github.com/dbt-labs/dbt-core/issues/5238), [#5292](https://github.com/dbt-labs/dbt-core/pull/5292))
-- Include schema file config in unrendered_config ([#5338](https://github.com/dbt-labs/dbt-core/issues/5338), [#5344](https://github.com/dbt-labs/dbt-core/pull/5344))
-- Resolves #5351 - Do not consider shorter varchar cols as schema changes ([#5351](https://github.com/dbt-labs/dbt-core/issues/5351), [#5395](https://github.com/dbt-labs/dbt-core/pull/5395))
-- on_shchma_change fail verbosity enhancement ([#5504](https://github.com/dbt-labs/dbt-core/issues/5504), [#5505](https://github.com/dbt-labs/dbt-core/pull/5505))
-- Fix error rendering docs block in metrics description ([#5585](https://github.com/dbt-labs/dbt-core/issues/5585), [#5603](https://github.com/dbt-labs/dbt-core/pull/5603))
-- Extended validations for the project names ([#5379](https://github.com/dbt-labs/dbt-core/issues/5379), [#5620](https://github.com/dbt-labs/dbt-core/pull/5620))
-- Use sys.exit instead of exit ([#5621](https://github.com/dbt-labs/dbt-core/issues/5621), [#5627](https://github.com/dbt-labs/dbt-core/pull/5627))
-- Finishing logic upgrade to Redshift for name truncation collisions. ([#5586](https://github.com/dbt-labs/dbt-core/issues/5586), [#5656](https://github.com/dbt-labs/dbt-core/pull/5656))
-- multiple args for ref and source ([#5634](https://github.com/dbt-labs/dbt-core/issues/5634), [#5635](https://github.com/dbt-labs/dbt-core/pull/5635))
-- Fix Unexpected behavior when chaining methods on dbt-ref'ed/sourced dataframes ([#5646](https://github.com/dbt-labs/dbt-core/issues/5646), [#5677](https://github.com/dbt-labs/dbt-core/pull/5677))
-
-### Docs
-
-- Leverages `docs.node_color` from `dbt-core` to color nodes in the DAG ([dbt-docs/#44](https://github.com/dbt-labs/dbt-docs/issues/44), [dbt-docs/#281](https://github.com/dbt-labs/dbt-docs/pull/281))
-
-### Under the Hood
-
-- Save use of default env vars to manifest to enable partial parsing in those cases. ([#5155](https://github.com/dbt-labs/dbt-core/issues/5155), [#5589](https://github.com/dbt-labs/dbt-core/pull/5589))
-- add more information to log line interop test failures ([#5658](https://github.com/dbt-labs/dbt-core/issues/5658), [#5659](https://github.com/dbt-labs/dbt-core/pull/5659))
-- Add supported languages to materializations ([#5569](https://github.com/dbt-labs/dbt-core/issues/5569), [#5695](https://github.com/dbt-labs/dbt-core/pull/5695))
-
-### Dependency
-
-- Bump python from 3.10.5-slim-bullseye to 3.10.6-slim-bullseye in /docker ([#4904](https://github.com/dbt-labs/dbt-core/issues/4904), [#5623](https://github.com/dbt-labs/dbt-core/pull/5623))
-- Bump mashumaro[msgpack] from 3.0.3 to 3.0.4 in /core ([#4904](https://github.com/dbt-labs/dbt-core/issues/4904), [#5649](https://github.com/dbt-labs/dbt-core/pull/5649))
-
-### Contributors
-- [@Goodkat](https://github.com/Goodkat) ([#5581](https://github.com/dbt-labs/dbt-core/pull/5581), [#5620](https://github.com/dbt-labs/dbt-core/pull/5620))
-- [@Ilanbenb](https://github.com/Ilanbenb) ([#5505](https://github.com/dbt-labs/dbt-core/pull/5505))
-- [@b-per](https://github.com/b-per) ([#5397](https://github.com/dbt-labs/dbt-core/pull/5397), [dbt-docs/#281](https://github.com/dbt-labs/dbt-docs/pull/281))
-- [@callum-mcdata](https://github.com/callum-mcdata) ([#5607](https://github.com/dbt-labs/dbt-core/pull/5607))
-- [@epapineau](https://github.com/epapineau) ([#5395](https://github.com/dbt-labs/dbt-core/pull/5395))
-- [@kadero](https://github.com/kadero) ([#4514](https://github.com/dbt-labs/dbt-core/pull/4514))
-- [@matt-winkler](https://github.com/matt-winkler) ([#5397](https://github.com/dbt-labs/dbt-core/pull/5397), [dbt-docs/#281](https://github.com/dbt-labs/dbt-docs/pull/281))
-- [@shrodingers](https://github.com/shrodingers) ([#5292](https://github.com/dbt-labs/dbt-core/pull/5292))
-- [@sungchun12](https://github.com/sungchun12) ([#5397](https://github.com/dbt-labs/dbt-core/pull/5397), [dbt-docs/#281](https://github.com/dbt-labs/dbt-docs/pull/281))
-- [@varun-dc](https://github.com/varun-dc) ([#5627](https://github.com/dbt-labs/dbt-core/pull/5627))
-
-
-## dbt-core 1.3.0-b1 - July 29, 2022
-### Features
-- Python model inital version ([#5261](https://github.com/dbt-labs/dbt-core/issues/5261), [#5421](https://github.com/dbt-labs/dbt-core/pull/5421))
-- allows user to include the file extension for .py models in the dbt run -m command. ([#5289](https://github.com/dbt-labs/dbt-core/issues/5289), [#5295](https://github.com/dbt-labs/dbt-core/pull/5295))
-- Incremental materialization refactor and cleanup ([#5245](https://github.com/dbt-labs/dbt-core/issues/5245), [#5359](https://github.com/dbt-labs/dbt-core/pull/5359))
-- Python models can support incremental logic ([#0](https://github.com/dbt-labs/dbt-core/issues/0), [#35](https://github.com/dbt-labs/dbt-core/pull/35))
-- Add reusable function for retrying adapter connections. Utilize said function to add retries for Postgres (and Redshift). ([#5022](https://github.com/dbt-labs/dbt-core/issues/5022), [#5432](https://github.com/dbt-labs/dbt-core/pull/5432))
-- add exponential backoff to connection retries on Postgres (and Redshift) ([#5502](https://github.com/dbt-labs/dbt-core/issues/5502), [#5503](https://github.com/dbt-labs/dbt-core/pull/5503))
-### Fixes
-- Add context to compilation errors generated while rendering generic test configuration values. ([#5294](https://github.com/dbt-labs/dbt-core/issues/5294), [#5393](https://github.com/dbt-labs/dbt-core/pull/5393))
-- Rename try to strict for more intuitiveness ([#5475](https://github.com/dbt-labs/dbt-core/issues/5475), [#5477](https://github.com/dbt-labs/dbt-core/pull/5477))
-- Ignore empty strings passed in as secrets ([#5312](https://github.com/dbt-labs/dbt-core/issues/5312), [#5518](https://github.com/dbt-labs/dbt-core/pull/5518))
-- Fix handling of top-level exceptions ([#5564](https://github.com/dbt-labs/dbt-core/issues/5564), [#5560](https://github.com/dbt-labs/dbt-core/pull/5560))
-### Docs
-- Update dependency inline-source from ^6.1.5 to ^7.2.0 ([#5574](https://github.com/dbt-labs/dbt-core/issues/5574), [#5577](https://github.com/dbt-labs/dbt-core/pull/5577))
-- Update dependency jest from ^26.2.2 to ^28.1.3 ([#5574](https://github.com/dbt-labs/dbt-core/issues/5574), [#5577](https://github.com/dbt-labs/dbt-core/pull/5577))
-- Update dependency underscore from ^1.9.0 to ^1.13.4 ([#5574](https://github.com/dbt-labs/dbt-core/issues/5574), [#5577](https://github.com/dbt-labs/dbt-core/pull/5577))
-- Update dependency webpack-cli from ^3.3.12 to ^4.7.0 ([#5574](https://github.com/dbt-labs/dbt-core/issues/5574), [#5577](https://github.com/dbt-labs/dbt-core/pull/5577))
-- Update dependency webpack-dev-server from ^3.1.11 to ^4.9.3 ([#5574](https://github.com/dbt-labs/dbt-core/issues/5574), [#5577](https://github.com/dbt-labs/dbt-core/pull/5577))
-- Searches no longer require perfect matches, and instead consider each word individually. `my model` or `model my` will now find `my_model`, without the need for underscores ([#5574](https://github.com/dbt-labs/dbt-core/issues/5574), [#5577](https://github.com/dbt-labs/dbt-core/pull/5577))
-- Support the renaming of SQL to code happening in dbt-core ([#5574](https://github.com/dbt-labs/dbt-core/issues/5574), [#5577](https://github.com/dbt-labs/dbt-core/pull/5577))
-### Under the Hood
-- Added language to tracked fields in run_model event ([#5571](https://github.com/dbt-labs/dbt-core/issues/5571), [#5469](https://github.com/dbt-labs/dbt-core/pull/5469))
-- Update mashumaro to 3.0.3 ([#4940](https://github.com/dbt-labs/dbt-core/issues/4940), [#5118](https://github.com/dbt-labs/dbt-core/pull/5118))
-- Add python incremental materialization test ([#0000](https://github.com/dbt-labs/dbt-core/issues/0000), [#5571](https://github.com/dbt-labs/dbt-core/pull/5571))
-### Dependencies
-- Upgrade to Jinja2==3.1.2 from Jinja2==2.11.3 ([#4748](https://github.com/dbt-labs/dbt-core/issues/4748), [#5465](https://github.com/dbt-labs/dbt-core/pull/5465))
-- Bump mypy from 0.961 to 0.971 ([#4904](https://github.com/dbt-labs/dbt-core/issues/4904), [#5495](https://github.com/dbt-labs/dbt-core/pull/5495))
-- Remove pin for MarkUpSafe from >=0.23,<2.1 ([#5506](https://github.com/dbt-labs/dbt-core/issues/5506), [#5507](https://github.com/dbt-labs/dbt-core/pull/5507))
-
-### Contributors
-- [@Goodkat](https://github.com/Goodkat) ([#5518](https://github.com/dbt-labs/dbt-core/pull/5518))
-- [@drewbanin](https://github.com/drewbanin) ([#5577](https://github.com/dbt-labs/dbt-core/pull/5577))
-- [@jeremyyeo](https://github.com/jeremyyeo) ([#5477](https://github.com/dbt-labs/dbt-core/pull/5477))
-- [@joellabes](https://github.com/joellabes) ([#5577](https://github.com/dbt-labs/dbt-core/pull/5577))
-- [@leoebfolsom](https://github.com/leoebfolsom) ([#5295](https://github.com/dbt-labs/dbt-core/pull/5295))
-- [@nicholasyager](https://github.com/nicholasyager) ([#5393](https://github.com/dbt-labs/dbt-core/pull/5393))
-- [@tomasfarias](https://github.com/tomasfarias) ([#5432](https://github.com/dbt-labs/dbt-core/pull/5432))
 
 ## Previous Releases
 

CONTRIBUTING.md

@@ -7,9 +7,7 @@
 3. [Setting up an environment](#setting-up-an-environment)
 4. [Running `dbt` in development](#running-dbt-core-in-development)
 5. [Testing dbt-core](#testing)
-6. [Debugging](#debugging)
-7. [Adding a changelog entry](#adding-a-changelog-entry)
-8. [Submitting a Pull Request](#submitting-a-pull-request)
+6. [Submitting a Pull Request](#submitting-a-pull-request)
 
 ## About this document
 
@@ -23,8 +21,7 @@ If you get stuck, we're happy to help! Drop us a line in the `#dbt-core-developm
 
 - **Adapters:** Is your issue or proposed code change related to a specific [database adapter](https://docs.getdbt.com/docs/available-adapters)? If so, please open issues, PRs, and discussions in that adapter's repository instead. The sole exception is Postgres; the `dbt-postgres` plugin lives in this repository (`dbt-core`).
 - **CLA:** Please note that anyone contributing code to `dbt-core` must sign the [Contributor License Agreement](https://docs.getdbt.com/docs/contributor-license-agreements). If you are unable to sign the CLA, the `dbt-core` maintainers will unfortunately be unable to merge any of your Pull Requests. We welcome you to participate in discussions, open issues, and comment on existing ones.
-- **Branches:** All pull requests from community contributors should target the `main` branch (default). If the change is needed as a patch for a minor version of dbt that has already been released (or is already a release candidate), a maintainer will backport the changes in your PR to the relevant "latest" release branch (`1.0.latest`, `1.1.latest`, ...). If an issue fix applies to a release branch, that fix should be first committed to the development branch and then to the release branch (rarely release-branch fixes may not apply to `main`).
-- **Releases**: Before releasing a new minor version of Core, we prepare a series of alphas and release candidates to allow users (especially employees of dbt Labs!) to test the new version in live environments. This is an important quality assurance step, as it exposes the new code to a wide variety of complicated deployments and can surface bugs before official release. Releases are accessible via pip, homebrew, and dbt Cloud.
+- **Branches:** All pull requests from community contributors should target the `main` branch (default). If the change is needed as a patch for a minor version of dbt that has already been released (or is already a release candidate), a maintainer will backport the changes in your PR to the relevant "latest" release branch (`1.0.latest`, `1.1.latest`, ...)
 
 ## Getting the code
 
@@ -44,9 +41,7 @@ If you are not a member of the `dbt-labs` GitHub organization, you can contribut
 
 ### dbt Labs contributors
 
-If you are a member of the `dbt-labs` GitHub organization, you will have push access to the `dbt-core` repo. Rather than forking `dbt-core` to make your changes, just clone the repository, check out a new branch, and push directly to that branch. Branch names should be fixed by `CT-XXX/` where:
-* CT stands for 'core team'
-* XXX stands for a JIRA ticket number
+If you are a member of the `dbt-labs` GitHub organization, you will have push access to the `dbt-core` repo. Rather than forking `dbt-core` to make your changes, just clone the repository, check out a new branch, and push directly to that branch.
 
 ## Setting up an environment
 
@@ -156,7 +151,7 @@ Check out the other targets in the Makefile to see other commonly used test
 suites.
 
 #### `pre-commit`
-[`pre-commit`](https://pre-commit.com) takes care of running all code-checks for formatting and linting. Run `make dev` to install `pre-commit` in your local environment (we recommend running this command with a python virtual environment active). This command installs several pip executables including black, mypy, and flake8. Once this is done you can use any of the linter-based make targets as well as a git pre-commit hook that will ensure proper formatting and linting.
+[`pre-commit`](https://pre-commit.com) takes care of running all code-checks for formatting and linting. Run `make dev` to install `pre-commit` in your local environment.  Once this is done you can use any of the linter-based make targets as well as a git pre-commit hook that will ensure proper formatting and linting.
 
 #### `tox`
 
@@ -179,29 +174,7 @@ python3 -m pytest tests/functional/sources
 
 > See [pytest usage docs](https://docs.pytest.org/en/6.2.x/usage.html) for an overview of useful command-line options.
 
-### Unit, Integration, Functional?
-
-Here are some general rules for adding tests:
-* unit tests (`test/unit` & `tests/unit`) don’t need to access a database; "pure Python" tests should be written as unit tests
-* functional tests (`test/integration` & `tests/functional`) cover anything that interacts with a database, namely adapter
-* *everything in* `test/*` *is being steadily migrated to* `tests/*`
-
-## Debugging
-
-1. The logs for a `dbt run` have stack traces and other information for debugging errors (in `logs/dbt.log` in your project directory).
-2. Try using a debugger, like `ipdb`. For pytest: `--pdb --pdbcls=IPython.terminal.debugger:pdb`
-3. Sometimes, it’s easier to debug on a single thread: `dbt --single-threaded run`
-4. To make print statements from Jinja macros:  `{{ log(msg, info=true) }}`
-5. You can also add `{{ debug() }}` statements, which will drop you into some auto-generated code that the macro wrote.
-6. The dbt “artifacts” are written out to the ‘target’ directory of your dbt project. They are in unformatted json, which can be hard to read. Format them with:
-> python -m json.tool target/run_results.json > run_results.json
-
-### Assorted development tips
-* Append `# type: ignore` to the end of a line if you need to disable `mypy` on that line.
-* Sometimes flake8 complains about lines that are actually fine, in which case you can put a comment on the line such as: # noqa or # noqa: ANNN, where ANNN is the error code that flake8 issues.
-* To collect output for `CProfile`, run dbt with the `-r` option and the name of an output file, i.e. `dbt -r dbt.cprof run`. If you just want to profile parsing, you can do: `dbt -r dbt.cprof parse`. `pip` install `snakeviz` to view the output. Run `snakeviz dbt.cprof` and output will be rendered in a browser window.
-
-## Adding a CHANGELOG Entry
+## Adding CHANGELOG Entry
 
 We use [changie](https://changie.dev) to generate `CHANGELOG` entries. **Note:** Do not edit the `CHANGELOG.md` directly. Your modifications will be lost.
 
@@ -213,10 +186,8 @@ You don't need to worry about which `dbt-core` version your change will go into.
 
 ## Submitting a Pull Request
 
-Code can be merged into the current development branch `main` by opening a pull request. A `dbt-core` maintainer will review your PR. They may suggest code revision for style or clarity, or request that you add unit or integration test(s). These are good things! We believe that, with a little bit of help, anyone can contribute high-quality code.
+A `dbt-core` maintainer will review your PR. They may suggest code revision for style or clarity, or request that you add unit or integration test(s). These are good things! We believe that, with a little bit of help, anyone can contribute high-quality code.
 
 Automated tests run via GitHub Actions. If you're a first-time contributor, all tests (including code checks and unit tests) will require a maintainer to approve. Changes in the `dbt-core` repository trigger integration tests against Postgres. dbt Labs also provides CI environments in which to test changes to other adapters, triggered by PRs in those adapters' repositories, as well as periodic maintenance checks of each adapter in concert with the latest `dbt-core` code changes.
 
 Once all tests are passing and your PR has been approved, a `dbt-core` maintainer will merge your changes into the active development branch. And that's it! Happy developing :tada:
-
-Sometimes, the content license agreement auto-check bot doesn't find a user's entry in its roster. If you need to force a rerun, add `@cla-bot check` in a comment on the pull request.

Makefile

@@ -6,19 +6,6 @@ ifeq ($(USE_DOCKER),true)
 	DOCKER_CMD := docker-compose run --rm test
 endif
 
-LOGS_DIR := ./logs
-
-# Optional flag to invoke tests using our CI env.
-# But we always want these active for structured
-# log testing.
-CI_FLAGS =\
-	DBT_TEST_USER_1=dbt_test_user_1\
-	DBT_TEST_USER_2=dbt_test_user_2\
-	DBT_TEST_USER_3=dbt_test_user_3\
-	RUSTFLAGS="-D warnings"\
-	LOG_DIR=./logs\
-	DBT_LOG_FORMAT=json
-
 .PHONY: dev
 dev: ## Installs dbt-* packages in develop mode along with development dependencies.
 	@\
@@ -61,20 +48,13 @@ test: .env ## Runs unit tests with py and code checks against staged changes.
 .PHONY: integration
 integration: .env ## Runs postgres integration tests with py-integration
 	@\
-	$(if $(USE_CI_FLAGS), $(CI_FLAGS)) $(DOCKER_CMD) tox -e py-integration -- -nauto
+	$(DOCKER_CMD) tox -e py-integration -- -nauto
 
 .PHONY: integration-fail-fast
 integration-fail-fast: .env ## Runs postgres integration tests with py-integration in "fail fast" mode.
 	@\
 	$(DOCKER_CMD) tox -e py-integration -- -x -nauto
 
-.PHONY: interop
-interop: clean
-	@\
-	mkdir $(LOGS_DIR) && \
-	$(CI_FLAGS) $(DOCKER_CMD) tox -e py-integration -- -nauto && \
-	LOG_DIR=$(LOGS_DIR) cargo run --manifest-path test/interop/log_parsing/Cargo.toml
-
 .PHONY: setup-db
 setup-db: ## Setup Postgres database with docker-compose for system testing.
 	@\
@@ -96,7 +76,6 @@ endif
 clean: ## Resets development environment.
 	@echo 'cleaning repo...'
 	@rm -f .coverage
-	@rm -f .coverage.*
 	@rm -rf .eggs/
 	@rm -f .env
 	@rm -rf .tox/

core/MANIFEST.in

@@ -1,2 +1 @@
 recursive-include dbt/include *.py *.sql *.yml *.html *.md .gitkeep .gitignore
-include dbt/py.typed

core/dbt/adapters/base/README.md

@@ -1,10 +0,0 @@
-
-## Base adapters
-
-### impl.py
-
-The class `SQLAdapter` in [base/imply.py](https://github.com/dbt-labs/dbt-core/blob/main/core/dbt/adapters/base/impl.py) is a (mostly) abstract object that adapter objects inherit from. The base class scaffolds out methods that every adapter project usually should implement for smooth communication between dbt and database.
-
-Some target databases require more or fewer methods--it all depends on what the warehouse's featureset is.
-
-Look into the class for function-level comments.

core/dbt/adapters/base/__init__.py

@@ -10,5 +10,5 @@ from dbt.adapters.base.relation import (  # noqa
     SchemaSearchMap,
 )
 from dbt.adapters.base.column import Column  # noqa
-from dbt.adapters.base.impl import AdapterConfig, BaseAdapter, PythonJobHelper  # noqa
+from dbt.adapters.base.impl import AdapterConfig, BaseAdapter  # noqa
 from dbt.adapters.base.plugin import AdapterPlugin  # noqa

core/dbt/adapters/base/impl.py

@@ -2,7 +2,6 @@ import abc
 from concurrent.futures import as_completed, Future
 from contextlib import contextmanager
 from datetime import datetime
-import time
 from itertools import chain
 from typing import (
     Optional,
@@ -43,12 +42,7 @@ from dbt.contracts.graph.manifest import Manifest, MacroManifest
 from dbt.contracts.graph.parsed import ParsedSeedNode
 from dbt.exceptions import warn_or_error
 from dbt.events.functions import fire_event
-from dbt.events.types import (
-    CacheMiss,
-    ListRelations,
-    CodeExecution,
-    CodeExecutionStatus,
-)
+from dbt.events.types import CacheMiss, ListRelations
 from dbt.utils import filter_null_values, executor
 
 from dbt.adapters.base.connections import Connection, AdapterResponse
@@ -60,7 +54,6 @@ from dbt.adapters.base.relation import (
     SchemaSearchMap,
 )
 from dbt.adapters.base import Column as BaseColumn
-from dbt.adapters.base import Credentials
 from dbt.adapters.cache import RelationsCache, _make_key
 
 
@@ -128,35 +121,6 @@ def _relation_name(rel: Optional[BaseRelation]) -> str:
         return str(rel)
 
 
-def log_code_execution(code_execution_function):
-    # decorator to log code and execution time
-    if code_execution_function.__name__ != "submit_python_job":
-        raise ValueError("this should be only used to log submit_python_job now")
-
-    def execution_with_log(*args):
-        self = args[0]
-        connection_name = self.connections.get_thread_connection().name
-        fire_event(CodeExecution(conn_name=connection_name, code_content=args[2]))
-        start_time = time.time()
-        response = code_execution_function(*args)
-        fire_event(
-            CodeExecutionStatus(
-                status=response._message, elapsed=round((time.time() - start_time), 2)
-            )
-        )
-        return response
-
-    return execution_with_log
-
-
-class PythonJobHelper:
-    def __init__(self, parsed_model: Dict, credential: Credentials) -> None:
-        raise NotImplementedError("PythonJobHelper is not implemented yet")
-
-    def submit(self, compiled_code: str) -> Any:
-        raise NotImplementedError("PythonJobHelper submit function is not implemented yet")
-
-
 class BaseAdapter(metaclass=AdapterMeta):
     """The BaseAdapter provides an abstract base class for adapters.
 
@@ -320,9 +284,7 @@ class BaseAdapter(metaclass=AdapterMeta):
             from dbt.parser.manifest import ManifestLoader
 
             manifest = ManifestLoader.load_macros(
-                self.config,
-                self.connections.set_query_header,
-                base_macros_only=base_macros_only,
+                self.config, self.connections.set_query_header, base_macros_only=base_macros_only
             )
             # TODO CT-211
             self._macro_manifest_lazy = manifest  # type: ignore[assignment]
@@ -341,11 +303,7 @@ class BaseAdapter(metaclass=AdapterMeta):
 
         if (database, schema) not in self.cache:
             fire_event(
-                CacheMiss(
-                    conn_name=self.nice_connection_name(),
-                    database=database,
-                    schema=schema,
-                )
+                CacheMiss(conn_name=self.nice_connection_name(), database=database, schema=schema)
             )
             return False
         else:
@@ -423,10 +381,7 @@ class BaseAdapter(metaclass=AdapterMeta):
         self.cache.update_schemas(cache_update)
 
     def set_relations_cache(
-        self,
-        manifest: Manifest,
-        clear: bool = False,
-        required_schemas: Set[BaseRelation] = None,
+        self, manifest: Manifest, clear: bool = False, required_schemas: Set[BaseRelation] = None
     ) -> None:
         """Run a query that gets a populated cache of the relations in the
         database and set the cache on this adapter.
@@ -715,10 +670,7 @@ class BaseAdapter(metaclass=AdapterMeta):
             return self.cache.get_relations(database, schema)
 
         schema_relation = self.Relation.create(
-            database=database,
-            schema=schema,
-            identifier="",
-            quote_policy=self.config.quoting,
+            database=database, schema=schema, identifier="", quote_policy=self.config.quoting
         ).without_identifier()
 
         # we can't build the relations cache because we don't have a
@@ -726,9 +678,7 @@ class BaseAdapter(metaclass=AdapterMeta):
         relations = self.list_relations_without_caching(schema_relation)
         fire_event(
             ListRelations(
-                database=database,
-                schema=schema,
-                relations=[_make_key(x) for x in relations],
+                database=database, schema=schema, relations=[_make_key(x) for x in relations]
             )
         )
 
@@ -1212,75 +1162,6 @@ class BaseAdapter(metaclass=AdapterMeta):
 
         return sql
 
-    @property
-    def python_submission_helpers(self) -> Dict[str, Type[PythonJobHelper]]:
-        raise NotImplementedError("python_submission_helpers is not specified")
-
-    @property
-    def default_python_submission_method(self) -> str:
-        raise NotImplementedError("default_python_submission_method is not specified")
-
-    @available.parse_none
-    @log_code_execution
-    def submit_python_job(self, parsed_model: dict, compiled_code: str) -> AdapterResponse:
-        submission_method = parsed_model["config"].get(
-            "submission_method", self.default_python_submission_method
-        )
-        if submission_method not in self.python_submission_helpers:
-            raise NotImplementedError(
-                "Submission method {} is not supported for current adapter".format(
-                    submission_method
-                )
-            )
-        job_helper = self.python_submission_helpers[submission_method](
-            parsed_model, self.connections.profile.credentials
-        )
-        submission_result = job_helper.submit(compiled_code)
-        # process submission result to generate adapter response
-        return self.generate_python_submission_response(submission_result)
-
-    def generate_python_submission_response(self, submission_result: Any) -> AdapterResponse:
-        raise NotImplementedException(
-            "Your adapter need to implement generate_python_submission_response"
-        )
-
-    def valid_incremental_strategies(self):
-        """The set of standard builtin strategies which this adapter supports out-of-the-box.
-        Not used to validate custom strategies defined by end users.
-        """
-        return ["append"]
-
-    def builtin_incremental_strategies(self):
-        return ["append", "delete+insert", "merge", "insert_overwrite"]
-
-    @available.parse_none
-    def get_incremental_strategy_macro(self, model_context, strategy: str):
-        # Construct macro_name from strategy name
-        if strategy is None:
-            strategy = "default"
-
-        # validate strategies for this adapter
-        valid_strategies = self.valid_incremental_strategies()
-        valid_strategies.append("default")
-        builtin_strategies = self.builtin_incremental_strategies()
-        if strategy in builtin_strategies and strategy not in valid_strategies:
-            raise RuntimeException(
-                f"The incremental strategy '{strategy}' is not valid for this adapter"
-            )
-
-        strategy = strategy.replace("+", "_")
-        macro_name = f"get_incremental_{strategy}_sql"
-        # The model_context should have MacroGenerator callable objects for all macros
-        if macro_name not in model_context:
-            raise RuntimeException(
-                'dbt could not find an incremental strategy macro with the name "{}" in {}'.format(
-                    macro_name, self.config.project_name
-                )
-            )
-
-        # This returns a callable macro
-        return model_context[macro_name]
-
 
 COLUMNS_EQUAL_SQL = """
 with diff_count as (

core/dbt/adapters/cache.py

@@ -1,4 +1,3 @@
-import re
 import threading
 from copy import deepcopy
 from typing import Any, Dict, Iterable, List, Optional, Set, Tuple
@@ -414,24 +413,9 @@ class RelationsCache:
         :raises InternalError: If the new key is already present.
         """
         if new_key in self.relations:
-            # Tell user when collision caused by model names truncated during
-            # materialization.
-            match = re.search("__dbt_backup|__dbt_tmp$", new_key.identifier)
-            if match:
-                truncated_model_name_prefix = new_key.identifier[: match.start()]
-                message_addendum = (
-                    "\n\nName collisions can occur when the length of two "
-                    "models' names approach your database's builtin limit. "
-                    "Try restructuring your project such that no two models "
-                    "share the prefix '{}'.".format(truncated_model_name_prefix)
-                    + " Then, clean your warehouse of any removed models."
-                )
-            else:
-                message_addendum = ""
-
             dbt.exceptions.raise_cache_inconsistent(
-                "in rename, new key {} already in cache: {}{}".format(
-                    new_key, list(self.relations.keys()), message_addendum
+                "in rename, new key {} already in cache: {}".format(
+                    new_key, list(self.relations.keys())
                 )
             )
 

core/dbt/cli/README.md

@@ -1 +0,0 @@
-TODO

core/dbt/cli/main.py

@@ -1,384 +0,0 @@
-import click
-from dbt.cli import params as p
-import sys
-
-# This is temporary for RAT-ing
-import inspect
-from pprint import pformat as pf
-
-
-# dbt
-@click.group(
-    invoke_without_command=True,
-    no_args_is_help=True,
-    epilog="Specify one of these sub-commands and you can find more help from there.",
-)
-@click.pass_context
-@p.version
-@p.cache_selected_only
-@p.debug
-@p.fail_fast
-@p.log_format
-@p.partial_parse
-@p.print
-@p.printer_width
-@p.quiet
-@p.send_anonymous_usage_stats
-@p.static_parser
-@p.use_colors
-@p.use_experimental_parser
-@p.version_check
-@p.warn_error
-@p.write_json
-@p.event_buffer_size
-@p.record_timing
-def cli(ctx, **kwargs):
-    """An ELT tool for managing your SQL transformations and data models.
-    For more documentation on these commands, visit: docs.getdbt.com
-    """
-    if kwargs.get("version", False):
-        click.echo(f"`version` called\n ctx.params: {pf(ctx.params)}")
-        sys.exit()
-    else:
-        del ctx.params["version"]
-
-
-# dbt build
-@cli.command("build")
-@click.pass_context
-def build(ctx, **kwargs):
-    """Run all Seeds, Models, Snapshots, and tests in DAG order"""
-    click.echo(
-        f"`{inspect.stack()[0][3]}` called\n kwargs: {kwargs}\n ctx: {pf(ctx.parent.params)}"
-    )
-
-
-# dbt clean
-@cli.command("clean")
-@click.pass_context
-@p.project_dir
-@p.profiles_dir
-@p.profile
-@p.target
-@p.vars
-def clean(ctx, **kwargs):
-    """Delete all folders in the clean-targets list (usually the dbt_packages and target directories.)"""
-    click.echo(
-        f"`{inspect.stack()[0][3]}` called\n kwargs: {kwargs}\n ctx: {pf(ctx.parent.params)}"
-    )
-
-
-# dbt docs
-@cli.group()
-@click.pass_context
-def docs(ctx, **kwargs):
-    """Generate or serve the documentation website for your project"""
-
-
-# dbt docs generate
-@docs.command("generate")
-@click.pass_context
-@p.version_check
-@p.project_dir
-@p.profiles_dir
-@p.profile
-@p.target
-@p.vars
-@p.compile_docs
-@p.defer
-@p.threads
-@p.target_path
-@p.log_path
-@p.models
-@p.exclude
-@p.selector
-@p.state
-def docs_generate(ctx, **kwargs):
-    """Generate the documentation website for your project"""
-    click.echo(
-        f"`{inspect.stack()[0][3]}` called\n kwargs: {kwargs}\n ctx: {pf(ctx.parent.parent.params)}"
-    )
-
-
-# dbt docs serve
-@docs.command("serve")
-@click.pass_context
-@p.project_dir
-@p.profiles_dir
-@p.profile
-@p.target
-@p.vars
-@p.port
-@p.browser
-def docs_serve(ctx, **kwargs):
-    """Serve the documentation website for your project"""
-    click.echo(
-        f"`{inspect.stack()[0][3]}` called\n kwargs: {kwargs}\n ctx: {pf(ctx.parent.parent.params)}"
-    )
-
-
-# dbt compile
-@cli.command("compile")
-@click.pass_context
-@p.version_check
-@p.project_dir
-@p.profiles_dir
-@p.profile
-@p.target
-@p.vars
-@p.parse_only
-@p.threads
-@p.target_path
-@p.log_path
-@p.models
-@p.exclude
-@p.selector
-@p.state
-@p.defer
-@p.full_refresh
-def compile(ctx, **kwargs):
-    """Generates executable SQL from source, model, test, and analysis files. Compiled SQL files are written to the target/ directory."""
-    click.echo(
-        f"`{inspect.stack()[0][3]}` called\n kwargs: {kwargs}\n ctx: {pf(ctx.parent.params)}"
-    )
-
-
-# dbt debug
-@cli.command("debug")
-@click.pass_context
-@p.version_check
-@p.project_dir
-@p.profiles_dir
-@p.profile
-@p.target
-@p.vars
-@p.config_dir
-def debug(ctx, **kwargs):
-    """Show some helpful information about dbt for debugging. Not to be confused with the --debug option which increases verbosity."""
-    click.echo(
-        f"`{inspect.stack()[0][3]}` called\n kwargs: {kwargs}\n ctx: {pf(ctx.parent.params)}"
-    )
-
-
-# dbt deps
-@cli.command("deps")
-@click.pass_context
-@p.profile
-@p.profiles_dir
-@p.project_dir
-@p.target
-@p.vars
-def deps(ctx, **kwargs):
-    """Pull the most recent version of the dependencies listed in packages.yml"""
-    click.echo(
-        f"`{inspect.stack()[0][3]}` called\n kwargs: {kwargs}\n ctx: {pf(ctx.parent.params)}"
-    )
-
-
-# dbt init
-@cli.command("init")
-@click.pass_context
-@p.profile
-@p.profiles_dir
-@p.project_dir
-@p.target
-@p.vars
-@p.skip_profile_setup
-def init(ctx, **kwargs):
-    """Initialize a new DBT project."""
-    click.echo(
-        f"`{inspect.stack()[0][3]}` called\n kwargs: {kwargs}\n ctx: {pf(ctx.parent.params)}"
-    )
-
-
-# dbt list
-# dbt TODO: Figure out aliasing for ls (or just c/p?)
-@cli.command("list")
-@click.pass_context
-@p.profile
-@p.profiles_dir
-@p.project_dir
-@p.target
-@p.vars
-@p.output
-@p.ouptut_keys
-@p.resource_type
-@p.models
-@p.indirect_selection
-@p.exclude
-@p.selector
-@p.state
-def list(ctx, **kwargs):
-    """List the resources in your project"""
-    click.echo(
-        f"`{inspect.stack()[0][3]}` called\n kwargs: {kwargs}\n ctx: {pf(ctx.parent.params)}"
-    )
-
-
-# dbt parse
-@cli.command("parse")
-@click.pass_context
-@p.profile
-@p.profiles_dir
-@p.project_dir
-@p.target
-@p.vars
-@p.write_manifest
-@p.compile_parse
-@p.threads
-@p.target_path
-@p.log_path
-@p.version_check
-def parse(ctx, **kwargs):
-    """Parses the project and provides information on performance"""
-    click.echo(
-        f"`{inspect.stack()[0][3]}` called\n kwargs: {kwargs}\n ctx: {pf(ctx.parent.params)}"
-    )
-
-
-# dbt run
-@cli.command("run")
-@click.pass_context
-@p.fail_fast
-@p.version_check
-@p.profile
-@p.profiles_dir
-@p.project_dir
-@p.target
-@p.vars
-@p.log_path
-@p.target_path
-@p.threads
-@p.models
-@p.exclude
-@p.selector
-@p.state
-@p.defer
-@p.full_refresh
-def run(ctx, **kwargs):
-    """Compile SQL and execute against the current target database."""
-    click.echo(
-        f"`{inspect.stack()[0][3]}` called\n kwargs: {kwargs}\n ctx: {pf(ctx.parent.params)}"
-    )
-
-
-# dbt run operation
-@cli.command("run-operation")
-@click.pass_context
-@p.profile
-@p.profiles_dir
-@p.project_dir
-@p.target
-@p.vars
-@p.args
-def run_operation(ctx, **kwargs):
-    """Run the named macro with any supplied arguments."""
-    click.echo(
-        f"`{inspect.stack()[0][3]}` called\n kwargs: {kwargs}\n ctx: {pf(ctx.parent.params)}"
-    )
-
-
-# dbt seed
-@cli.command("seed")
-@click.pass_context
-@p.version_check
-@p.profile
-@p.profiles_dir
-@p.project_dir
-@p.target
-@p.vars
-@p.full_refresh
-@p.log_path
-@p.target_path
-@p.threads
-@p.models
-@p.exclude
-@p.selector
-@p.state
-@p.show
-def seed(ctx, **kwargs):
-    """Load data from csv files into your data warehouse."""
-    click.echo(
-        f"`{inspect.stack()[0][3]}` called\n kwargs: {kwargs}\n ctx: {pf(ctx.parent.params)}"
-    )
-
-
-# dbt snapshot
-@cli.command("snapshot")
-@click.pass_context
-@p.profile
-@p.profiles_dir
-@p.project_dir
-@p.target
-@p.vars
-@p.threads
-@p.models
-@p.exclude
-@p.selector
-@p.state
-@p.defer
-def snapshot(ctx, **kwargs):
-    """Execute snapshots defined in your project"""
-    click.echo(
-        f"`{inspect.stack()[0][3]}` called\n kwargs: {kwargs}\n ctx: {pf(ctx.parent.params)}"
-    )
-
-
-# dbt source
-@cli.group()
-@click.pass_context
-def source(ctx, **kwargs):
-    """Manage your project's sources"""
-
-
-# dbt source freshness
-@source.command("freshness")
-@click.pass_context
-@p.profile
-@p.profiles_dir
-@p.project_dir
-@p.target
-@p.vars
-@p.threads
-@p.models
-@p.exclude
-@p.selector
-@p.state
-@p.output_path  # TODO: Is this ok to re-use?  We have three different output params, how much can we consolidate?
-def freshness(ctx, **kwargs):
-    """Snapshots the current freshness of the project's sources"""
-    click.echo(
-        f"`{inspect.stack()[0][3]}` called\n kwargs: {kwargs}\n ctx: {pf(ctx.parent.parent.params)}"
-    )
-
-
-# dbt test
-@cli.command("test")
-@click.pass_context
-@p.fail_fast
-@p.version_check
-@p.store_failures
-@p.profile
-@p.profiles_dir
-@p.project_dir
-@p.target
-@p.vars
-@p.indirect_selection
-@p.log_path
-@p.target_path
-@p.threads
-@p.models
-@p.exclude
-@p.selector
-@p.state
-@p.defer
-def test(ctx, **kwargs):
-    """Runs tests on data in deployed models. Run this after `dbt run`"""
-    click.echo(
-        f"`{inspect.stack()[0][3]}` called\n kwargs: {kwargs}\n ctx: {pf(ctx.parent.params)}"
-    )
-
-
-# Support running as a module
-if __name__ == "__main__":
-    cli()

core/dbt/cli/params.py

@@ -1,304 +0,0 @@
-import click
-import yaml
-from pathlib import Path, PurePath
-from click import ParamType
-
-
-class YAML(ParamType):
-    """The Click YAML type. Converts YAML strings into objects."""
-
-    name = "YAML"
-
-    def convert(self, value, param, ctx):
-        # assume non-string values are a problem
-        if not isinstance(value, str):
-            self.fail(f"Cannot load YAML from type {type(value)}", param, ctx)
-        try:
-            return yaml.load(value, Loader=yaml.Loader)
-        except yaml.parser.ParserError:
-            self.fail(f"String '{value}' is not valid YAML", param, ctx)
-
-
-args = click.option(
-    "--args",
-    help="Supply arguments to the macro. This dictionary will be mapped to the keyword arguments defined in the selected macro. This argument should be a YAML string, eg. '{my_variable: my_value}'",
-    type=YAML(),
-)
-
-browser = click.option(
-    "--browser/--no-browser",
-    help="Wether or not to open a local web browser after starting the server",
-    default=True,
-)
-
-cache_selected_only = click.option(
-    "--cache-selected-only/--no-cache-selected-only",
-    help="Pre cache database objects relevant to selected resource only.",
-    default=False,
-)
-
-compile_docs = click.option(
-    "--compile/--no-compile",
-    help="Wether or not to run 'dbt compile' as part of docs generation",
-    default=True,
-)
-
-compile_parse = click.option(
-    "--compile/--no-compile",
-    help="TODO: No help text currently available",
-    default=True,
-)
-
-config_dir = click.option(
-    "--config-dir",
-    help="If specified, DBT will show path information for this project",
-    type=click.STRING,
-)
-
-debug = click.option(
-    "--debug/--no-debug",
-    "-d/ ",
-    help="Display debug logging during dbt execution. Useful for debugging and making bug reports.",
-    default=False,
-)
-
-defer = click.option(
-    "--defer/--no-defer",
-    help="If set, defer to the state variable for resolving unselected nodes.",
-    default=True,
-)
-
-event_buffer_size = click.option(
-    "--event-buffer-size",
-    help="Sets the max number of events to buffer in EVENT_HISTORY.",
-    default=100000,
-    type=click.INT,
-)
-
-exclude = click.option("--exclude", help="Specify the nodes to exclude.")
-
-fail_fast = click.option(
-    "--fail-fast/--no-fail-fast", "-x/ ", help="Stop execution on first failure.", default=False
-)
-
-full_refresh = click.option(
-    "--full-refresh",
-    help="If specified, dbt will drop incremental models and fully-recalculate the incremental table from the model definition.",
-    is_flag=True,
-)
-
-indirect_selection = click.option(
-    "--indirect_selection",
-    help="Select all tests that are adjacent to selected resources, even if they those resources have been explicitly selected.",
-    type=click.Choice(["eager", "cautious"], case_sensitive=False),
-    default="eager",
-)
-
-log_format = click.option(
-    "--log-format",
-    help="Specify the log format, overriding the command's default.",
-    type=click.Choice(["text", "json", "default"], case_sensitive=False),
-    default="default",
-)
-
-log_path = click.option(
-    "--log-path",
-    help="Configure the 'log-path'. Only applies this setting for the current run. Overrides the 'DBT_LOG_PATH' if it is set.",
-    type=click.Path(),
-)
-
-models = click.option("-m", "-s", help="Specify the nodes to include.", multiple=True)
-
-output = click.option(
-    "--output",
-    help="TODO: No current help text",
-    type=click.Choice(["json", "name", "path", "selector"], case_sensitive=False),
-    default="name",
-)
-
-ouptut_keys = click.option(
-    "--output-keys",
-    help="TODO: No current help text",
-    default=False,
-)
-
-output_path = click.option(
-    "--output",
-    "-o",
-    help="Specify the output path for the json report. By default, outputs to 'target/sources.json'",
-    type=click.Path(file_okay=True, dir_okay=False, writable=True),
-    default=PurePath.joinpath(Path.cwd(), "target/sources.json"),
-)
-
-parse_only = click.option(
-    "--parse-only",
-    help="TODO:  No help text currently available",
-    is_flag=True,
-)
-
-partial_parse = click.option(
-    "--partial-parse/--no-partial-parse",
-    help="Allow for partial parsing by looking for and writing to a pickle file in the target directory. This overrides the user configuration file.",
-    default=True,
-)
-
-port = click.option(
-    "--port", help="Specify the port number for the docs server", default=8080, type=click.INT
-)
-
-print = click.option(
-    "--print/--no-print", help="Output all {{ print() }} macro calls.", default=True
-)
-
-printer_width = click.option(
-    "--printer_width", help="Sets the width of terminal output", type=click.INT, default=80
-)
-
-profile = click.option(
-    "--profile",
-    help="Which profile to load. Overrides setting in dbt_project.yml.",
-)
-
-profiles_dir = click.option(
-    "--profiles-dir",
-    help=f"Which directory to look in for the profiles.yml file. Default = {PurePath.joinpath(Path.home(), '.dbt')}",
-    default=PurePath.joinpath(Path.home(), ".dbt"),
-    type=click.Path(
-        exists=True,
-    ),
-)
-
-project_dir = click.option(
-    "--project-dir",
-    help="Which directory to look in for the dbt_project.yml file. Default is the current working directory and its parents.",
-    default=Path.cwd(),
-    type=click.Path(exists=True),
-)
-
-quiet = click.option(
-    "--quiet/--no-quiet",
-    help="Suppress all non-error logging to stdout. Does not affect {{ print() }} macro calls.",
-    default=False,
-)
-
-record_timing = click.option(
-    "-r",
-    "--record-timing-info",
-    help="When this option is passed, dbt will output low-level timing stats to the specified file. Example: `--record-timing-info output.profile`",
-    is_flag=True,
-    default=False,
-)
-
-resource_type = click.option(
-    "--resource-type",
-    help="TODO: No current help text",
-    type=click.Choice(
-        [
-            "metric",
-            "source",
-            "analysis",
-            "model",
-            "test",
-            "exposure",
-            "snapshot",
-            "seed",
-            "default",
-            "all",
-        ],
-        case_sensitive=False,
-    ),
-    default="default",
-)
-
-selector = click.option("--selector", help="The selector name to use, as defined in selectors.yml")
-
-send_anonymous_usage_stats = click.option(
-    "--anonymous-usage-stats/--no-anonymous-usage-stats",
-    help="Send anonymous usage stats to dbt Labs.",
-    default=True,
-)
-
-show = click.option(
-    "--show",
-    help="Show a sample of the loaded data in the terminal",
-    default=False,
-)
-
-skip_profile_setup = click.option(
-    "--skip-profile-setup",
-    "-s",
-    help="Skip interative profile setup.",
-    default=False,
-)
-
-state = click.option(
-    "--state",
-    help="If set, use the given directory as the source for json files to compare with this project.",
-)
-
-static_parser = click.option(
-    "--static-parser/--no-static-parser", help="Use the static parser.", default=True
-)
-
-store_failures = click.option(
-    "--store-failures", help="Store test results (failing rows) in the database", default=False
-)
-
-target = click.option("-t", "--target", help="Which target to load for the given profile")
-
-target_path = click.option(
-    "--target-path",
-    help="Configure the 'target-path'. Only applies this setting for the current run. Overrides the 'DBT_TARGET_PATH' if it is set.",
-    type=click.Path(),
-)
-
-threads = click.option(
-    "--threads",
-    help="Specify number of threads to use while executing models. Overrides settings in profiles.yml.",
-    default=1,
-    type=click.INT,
-)
-
-use_colors = click.option(
-    "--use-colors/--no-use-colors",
-    help="Output is colorized by default and may also be set in a profile or at the command line.",
-    default=True,
-)
-
-use_experimental_parser = click.option(
-    "--use-experimental-parser/--no-use-experimental-parser",
-    help="Enable experimental parsing features.",
-    default=False,
-)
-
-vars = click.option(
-    "--vars",
-    help="Supply variables to the project. This argument overrides variables defined in your dbt_project.yml file. This argument should be a YAML string, eg. '{my_variable: my_value}'",
-    type=YAML(),
-)
-
-version = click.option("--version", help="Show version information", is_flag=True, default=False)
-
-version_check = click.option(
-    "--version-check/--no-version-check",
-    help="Ensure dbt's version matches the one specified in the dbt_project.yml file ('require-dbt-version')",
-    default=True,
-)
-
-warn_error = click.option(
-    "--warn-error/--no-warn-error",
-    help="If dbt would normally warn, instead raise an exception. Examples include --models that selects nothing, deprecations, configurations with no associated models, invalid test configurations, and missing sources/refs in tests.",
-    default=False,
-)
-
-write_json = click.option(
-    "--write-json/--no-write-json",
-    help="Writing the manifest and run_results.json files to disk",
-    default=True,
-)
-
-write_manifest = click.option(
-    "--write-manifest/--no-write-manifest",
-    help="TODO: No help text currently available",
-    default=True,
-)

core/dbt/clients/README.md

@@ -1,19 +1 @@
 # Clients README
-
-### Jinja
-
-#### How are materializations defined
-
-Model materializations are kept in `core/dbt/include/global_project/macros/materializations/models/`. Materializations are defined using syntax that isn't part of the Jinja standard library. These tags are referenced internally, and materializations can be overridden in user projects when users have specific needs.
-
-```
--- Pseudocode for arguments
-{% materialization <name>, <target name := one_of{default, adapter}> %}'
-…
-{% endmaterialization %}
-```
-
-These blocks are referred to Jinja extensions. Extensions are defined as part of the accepted Jinja code encapsulated within a dbt project. This includes system code used internally by dbt and user space (i.e. user-defined) macros. Extensions exist to help Jinja users create reusable code blocks or abstract objects--for us, materializations are a great use-case since we pass these around as arguments within dbt system code.
-
-The code that defines this extension is a class `MaterializationExtension` and a `parse` routine. That code lives in [clients/jinja.py](https://github.com/dbt-labs/dbt-core/blob/main/core/dbt/clients/jinja.py). The routine
-enables Jinja to parse (i.e. recognize) the unique comma separated arg structure our `materialization` tags exhibit (the `table, default` as seen above).

core/dbt/clients/jinja.py

@@ -37,10 +37,6 @@ from dbt.exceptions import (
     UndefinedMacroException,
 )
 from dbt import flags
-from dbt.node_types import ModelLanguage
-
-
-SUPPORTED_LANG_ARG = jinja2.nodes.Name("supported_languages", "param")
 
 
 def _linecache_inject(source, write):
@@ -165,7 +161,7 @@ def quoted_native_concat(nodes):
 
 
 class NativeSandboxTemplate(jinja2.nativetypes.NativeTemplate):  # mypy: ignore
-    environment_class = NativeSandboxEnvironment  # type: ignore
+    environment_class = NativeSandboxEnvironment
 
     def render(self, *args, **kwargs):
         """Render the template to produce a native Python type. If the
@@ -311,7 +307,7 @@ class MacroGenerator(BaseMacroGenerator):
             unique_id = self.macro.unique_id
             depth = self.stack.depth
             # only mark depth=0 as a dependency
-            if depth == 1:
+            if depth == 0:
                 self.node.depends_on.add_macro(unique_id)
             self.stack.push(unique_id)
             try:
@@ -368,20 +364,9 @@ class MaterializationExtension(jinja2.ext.Extension):
                 value = parser.parse_expression()
                 adapter_name = value.value
 
-            elif target.name == "supported_languages":
-                target.set_ctx("param")
-                node.args.append(target)
-                parser.stream.expect("assign")
-                languages = parser.parse_expression()
-                node.defaults.append(languages)
-
             else:
                 invalid_materialization_argument(materialization_name, target.name)
 
-        if SUPPORTED_LANG_ARG not in node.args:
-            node.args.append(SUPPORTED_LANG_ARG)
-            node.defaults.append(jinja2.nodes.List([jinja2.nodes.Const("sql")]))
-
         node.name = get_materialization_macro_name(materialization_name, adapter_name)
 
         node.body = parser.parse_statements(("name:endmaterialization",), drop_needle=True)
@@ -647,21 +632,3 @@ def add_rendered_test_kwargs(
     # when the test node was created in _parse_generic_test.
     kwargs = deep_map_render(_convert_function, node.test_metadata.kwargs)
     context[GENERIC_TEST_KWARGS_NAME] = kwargs
-
-
-def get_supported_languages(node: jinja2.nodes.Macro) -> List[ModelLanguage]:
-    if "materialization" not in node.name:
-        raise_compiler_error("Only materialization macros can be used with this function")
-
-    no_kwargs = not node.defaults
-    no_langs_found = SUPPORTED_LANG_ARG not in node.args
-
-    if no_kwargs or no_langs_found:
-        raise_compiler_error(f"No supported_languages found in materialization macro {node.name}")
-
-    lang_idx = node.args.index(SUPPORTED_LANG_ARG)
-    # indexing defaults from the end
-    # since supported_languages is a kwarg, and kwargs are at always after args
-    return [
-        ModelLanguage[item.value] for item in node.defaults[-(len(node.args) - lang_idx)].items
-    ]

core/dbt/clients/registry.py

@@ -14,7 +14,6 @@ from dbt.events.types import (
 )
 from dbt.utils import memoized, _connection_exception_retry as connection_exception_retry
 from dbt import deprecations
-from dbt import semver
 import os
 
 if os.getenv("DBT_PACKAGE_HUB_URL"):
@@ -126,37 +125,10 @@ def package_version(package_name, version, registry_base_url=None) -> Dict[str,
     return response[version]
 
 
-def is_compatible_version(package_spec, dbt_version) -> bool:
-    require_dbt_version = package_spec.get("require_dbt_version")
-    if not require_dbt_version:
-        # if version requirements are missing or empty, assume any version is compatible
-        return True
-    else:
-        # determine whether dbt_version satisfies this package's require-dbt-version config
-        if not isinstance(require_dbt_version, list):
-            require_dbt_version = [require_dbt_version]
-        supported_versions = [
-            semver.VersionSpecifier.from_version_string(v) for v in require_dbt_version
-        ]
-        return semver.versions_compatible(dbt_version, *supported_versions)
-
-
-def get_compatible_versions(package_name, dbt_version, should_version_check) -> List["str"]:
+def get_available_versions(package_name) -> List["str"]:
     # returns a list of all available versions of a package
     response = package(package_name)
-
-    # if the user doesn't care about installing compatible versions, just return them all
-    if not should_version_check:
-        return list(response)
-
-    # otherwise, only return versions that are compatible with the installed version of dbt-core
-    else:
-        compatible_versions = [
-            pkg_version
-            for pkg_version, info in response.items()
-            if is_compatible_version(info, dbt_version)
-        ]
-        return compatible_versions
+    return list(response)
 
 
 def _get_index(registry_base_url=None):

core/dbt/compilation.py

@@ -29,7 +29,7 @@ from dbt.exceptions import (
 from dbt.graph import Graph
 from dbt.events.functions import fire_event
 from dbt.events.types import FoundStats, CompilingNode, WritingInjectedSQLForNode
-from dbt.node_types import NodeType, ModelLanguage
+from dbt.node_types import NodeType
 from dbt.events.format import pluralize
 import dbt.tracking
 
@@ -271,7 +271,7 @@ class Compiler:
         are rolled up into the models that refer to them by
         inserting CTEs into the SQL.
         """
-        if model.compiled_code is None:
+        if model.compiled_sql is None:
             raise RuntimeException("Cannot inject ctes into an unparsed node", model)
         if model.extra_ctes_injected:
             return (model, model.extra_ctes)
@@ -324,28 +324,29 @@ class Compiler:
             _extend_prepended_ctes(prepended_ctes, new_prepended_ctes)
 
             new_cte_name = self.add_ephemeral_prefix(cte_model.name)
-            rendered_sql = cte_model._pre_injected_sql or cte_model.compiled_code
+            rendered_sql = cte_model._pre_injected_sql or cte_model.compiled_sql
             sql = f" {new_cte_name} as (\n{rendered_sql}\n)"
 
             _add_prepended_cte(prepended_ctes, InjectedCTE(id=cte.id, sql=sql))
 
         injected_sql = self._inject_ctes_into_sql(
-            model.compiled_code,
+            model.compiled_sql,
             prepended_ctes,
         )
-        model._pre_injected_sql = model.compiled_code
-        model.compiled_code = injected_sql
+        model._pre_injected_sql = model.compiled_sql
+        model.compiled_sql = injected_sql
         model.extra_ctes_injected = True
         model.extra_ctes = prepended_ctes
         model.validate(model.to_dict(omit_none=True))
+
         manifest.update_node(model)
 
         return model, prepended_ctes
 
     # creates a compiled_node from the ManifestNode passed in,
     # creates a "context" dictionary for jinja rendering,
-    # and then renders the "compiled_code" using the node, the
-    # raw_code and the context.
+    # and then renders the "compiled_sql" using the node, the
+    # raw_sql and the context.
     def _compile_node(
         self,
         node: ManifestNode,
@@ -361,40 +362,20 @@ class Compiler:
         data.update(
             {
                 "compiled": False,
-                "compiled_code": None,
+                "compiled_sql": None,
                 "extra_ctes_injected": False,
                 "extra_ctes": [],
             }
         )
         compiled_node = _compiled_type_for(node).from_dict(data)
 
-        if compiled_node.language == ModelLanguage.python:
-            # TODO could we also 'minify' this code at all? just aesthetic, not functional
+        context = self._create_node_context(compiled_node, manifest, extra_context)
 
-            # quoating seems like something very specific to sql so far
-            # for all python implementations we are seeing there's no quating.
-            # TODO try to find better way to do this, given that
-            original_quoting = self.config.quoting
-            self.config.quoting = {key: False for key in original_quoting.keys()}
-            context = self._create_node_context(compiled_node, manifest, extra_context)
-
-            postfix = jinja.get_rendered(
-                "{{ py_script_postfix(model) }}",
-                context,
-                node,
-            )
-            # we should NOT jinja render the python model's 'raw code'
-            compiled_node.compiled_code = f"{node.raw_code}\n\n{postfix}"
-            # restore quoting settings in the end since context is lazy evaluated
-            self.config.quoting = original_quoting
-
-        else:
-            context = self._create_node_context(compiled_node, manifest, extra_context)
-            compiled_node.compiled_code = jinja.get_rendered(
-                node.raw_code,
-                context,
-                node,
-            )
+        compiled_node.compiled_sql = jinja.get_rendered(
+            node.raw_sql,
+            context,
+            node,
+        )
 
         compiled_node.relation_name = self._get_relation_name(node)
 
@@ -506,15 +487,15 @@ class Compiler:
 
         return Graph(linker.graph)
 
-    # writes the "compiled_code" into the target/compiled directory
+    # writes the "compiled_sql" into the target/compiled directory
     def _write_node(self, node: NonSourceCompiledNode) -> ManifestNode:
         if not node.extra_ctes_injected or node.resource_type == NodeType.Snapshot:
             return node
         fire_event(WritingInjectedSQLForNode(unique_id=node.unique_id))
 
-        if node.compiled_code:
+        if node.compiled_sql:
             node.compiled_path = node.write_node(
-                self.config.target_path, "compiled", node.compiled_code
+                self.config.target_path, "compiled", node.compiled_sql
             )
         return node
 

core/dbt/config/project.py

@@ -380,8 +380,6 @@ class PartialProject(RenderComponents):
         snapshots: Dict[str, Any]
         sources: Dict[str, Any]
         tests: Dict[str, Any]
-        metrics: Dict[str, Any]
-        exposures: Dict[str, Any]
         vars_value: VarProvider
 
         dispatch = cfg.dispatch
@@ -390,8 +388,6 @@ class PartialProject(RenderComponents):
         snapshots = cfg.snapshots
         sources = cfg.sources
         tests = cfg.tests
-        metrics = cfg.metrics
-        exposures = cfg.exposures
         if cfg.vars is None:
             vars_dict: Dict[str, Any] = {}
         else:
@@ -445,8 +441,6 @@ class PartialProject(RenderComponents):
             query_comment=query_comment,
             sources=sources,
             tests=tests,
-            metrics=metrics,
-            exposures=exposures,
             vars=vars_value,
             config_version=cfg.config_version,
             unrendered=unrendered,
@@ -549,8 +543,6 @@ class Project:
     snapshots: Dict[str, Any]
     sources: Dict[str, Any]
     tests: Dict[str, Any]
-    metrics: Dict[str, Any]
-    exposures: Dict[str, Any]
     vars: VarProvider
     dbt_version: List[VersionSpecifier]
     packages: Dict[str, Any]
@@ -623,8 +615,6 @@ class Project:
                 "snapshots": self.snapshots,
                 "sources": self.sources,
                 "tests": self.tests,
-                "metrics": self.metrics,
-                "exposures": self.exposures,
                 "vars": self.vars.to_dict(),
                 "require-dbt-version": [v.to_version_string() for v in self.dbt_version],
                 "config-version": self.config_version,

core/dbt/config/renderer.py

@@ -3,13 +3,13 @@ import re
 import os
 
 from dbt.clients.jinja import get_rendered, catch_jinja
-from dbt.constants import SECRET_ENV_PREFIX
 from dbt.context.target import TargetContext
 from dbt.context.secret import SecretContext, SECRET_PLACEHOLDER
 from dbt.context.base import BaseContext
 from dbt.contracts.connection import HasCredentials
 from dbt.exceptions import DbtProjectError, CompilationException, RecursionException
 from dbt.utils import deep_map_render
+from dbt.logger import SECRET_ENV_PREFIX
 
 
 Keypath = Tuple[Union[str, int], ...]

core/dbt/config/runtime.py

@@ -105,8 +105,6 @@ class RuntimeConfig(Project, Profile, AdapterRequiredConfig):
             query_comment=project.query_comment,
             sources=project.sources,
             tests=project.tests,
-            metrics=project.metrics,
-            exposures=project.exposures,
             vars=project.vars,
             config_version=project.config_version,
             unrendered=project.unrendered,
@@ -276,8 +274,6 @@ class RuntimeConfig(Project, Profile, AdapterRequiredConfig):
             "snapshots": self._get_config_paths(self.snapshots),
             "sources": self._get_config_paths(self.sources),
             "tests": self._get_config_paths(self.tests),
-            "metrics": self._get_config_paths(self.metrics),
-            "exposures": self._get_config_paths(self.exposures),
         }
 
     def get_unused_resource_config_paths(
@@ -481,8 +477,6 @@ class UnsetProfileConfig(RuntimeConfig):
                 "snapshots": self.snapshots,
                 "sources": self.sources,
                 "tests": self.tests,
-                "metrics": self.metrics,
-                "exposures": self.exposures,
                 "vars": self.vars.to_dict(),
                 "require-dbt-version": [v.to_version_string() for v in self.dbt_version],
                 "config-version": self.config_version,
@@ -543,8 +537,6 @@ class UnsetProfileConfig(RuntimeConfig):
             query_comment=project.query_comment,
             sources=project.sources,
             tests=project.tests,
-            metrics=project.metrics,
-            exposures=project.exposures,
             vars=project.vars,
             config_version=project.config_version,
             unrendered=project.unrendered,