Dbt-teradata

Features
* Added support for insert_by_period materialization

Fixes
* Fix at_least_one macro

Under the hood
* Removed custom test suite

---

Fixes
* Fix get_tables_by_pattern_sql macro

---

Features
* Newly added macros (at_least_one, deduplicate, expression_is_true, generate_surrogate_key)
* Updated python and dbt-core dependency

Fixes
* Removed cross-db macros as they have been moved to dbt-teradata
Docs

Under the hood
* Added a test patch files to test dbt-utils macros against db-teradata

---

1. Update [`CHANGELOG.md`](CHANGELOG.md) with the most recent changes
1. Bump the version using [`bump2version`](https://github.com/c4urself/bump2version/#bump2version):
1. Dry run first by running:

bumpversion --dry-run --verbose --new-version <desired-version> <part>


Some examples:
- Release candidates: `--new-version 0.10.2rc1 num`
- Alpha releases: `--new-version 0.10.2a1 num`
- Patch releases: `--new-version 0.10.2.1 patch`
- Minor releases: `--new-version 0.11.0.1 minor`
- Major releases: `--new-version 1.0.0.1 major`
1. Actually modify the files, tag and commit to git:

bumpversion --tag --commit --new-version <desired-version> <part>

1. Push change to the origin:

git push origin
git push origin --tags


PyPI

1. remove existing source distribution:

rm -fr dist/*

1. Build source distribution:

python setup.py sdist bdist_wheel

1. Deploy to Test PyPi:

twine upload -r testpypi dist/*

1. Verity the library at https://test.pypi.org/project/dbt-teradata/.
1. Deploy to PyPi:

twine upload dist/*

1. Verify at https://pypi.org/project/dbt-teradata/

PyPi recognizes [pre-release versioning conventions](https://packaging.python.org/guides/distributing-packages-using-setuptools/#pre-release-versioning) and will label "pre-releases" as-such.

GitHub

1. Click the [Create a new release](https://github.com/Teradata/dbt-teradata/releases/new) link on the project homepage in GitHub

Features

Fixes

Docs

Under the hood

1. For pre-releases:
- leave the description blank
- Tick the "this is a pre-release" checkbox
1. Click the "publish release" button


Release process

Git
1. Make sure you are on `main` branch:

git checkout main

1. Verify, that `CHANGELOG.md` contains all the changes for the release.
1. Create a tag and push to origin:

git tag v0.0.1
git push origin --tags


GitHub

1. Click the [Create a new release](https://github.com/Teradata/dbt-teradata-utils/releases/new) link on the project homepage in GitHub