generate_model_yaml
withupstream_descriptions=True
now reads from upstream sources in addition to models.(#112)[#112]generate_source
now has options for case sensitivity in all fields (#112
- Column
description
fields are now correctly escaped ingenerate_model_yaml
(#142)
- Fixed
generate_source
documentation - Rewrote the contributor README at
integration_tests/README.md
- @wircho made their first contribution in #159
- @yatsky made their first contribution in #164
- @pnadolny made their first contribution in #168
- @esegal made their first contribution in #154
- @gwenwindflower made their first contribution in #163
Full Changelog: https://github.com/dbt-labs/dbt-codegen/compare/0.11.0...0.12.0-b1
include_data_types
parameter added to generate_model_yaml
and behavior changed for generate_source
. Both default to true
and are lowercase to align with the dbt style guide. Scale & precision are not included. Previous logic for generate_source
defaulted to false
and the resulting data types were uppercase and included scale & precision (#122).
Dispatch can be used to utilize the column data type formatting of previous versions. Namely, by adding this macro to your project:
{% macro default__data_type_format_source(column) %}
{{ return(column.data_type | upper) }}
{% endmacro %}
And then adding this within dbt_project.yml
:
dispatch:
- macro_namespace: codegen
search_order: ["my_project", "codegen"]
- GitHub Action to add/remove triage labels as-needed by @dbeatty10 in #133
- GitHub Action to close issues as stale as-needed by @dbeatty10 in #134
- Update README.md by @cohms in #129
- Remove hard-coded values for database and schema by @dbeatty10 in #139
- Instructions for the release process by @dbeatty10 in #137
- Add
include_data_types
argument togenerate_model_yaml
macro by @linbug in #122
Full Changelog: https://github.com/dbt-labs/dbt-codegen/compare/0.10.0...v0.10.0
- added comments to verbose regex in generate_model_import_ctes by @graciegoheen in #93
- Feature/hackathon model generator by @fivetran-joemarkiewicz in #83
- Suggestion to include packages.yml example in README.md by @Maayan-s in #77
- Add include_data_types flag to generate_source macro by @GSokol in #76
- Expected result of nested struct in BigQuery by @dbeatty10 in #105
- issue106/get_models helper macro by @erkanncelen in #115
- Feat/generate sources add database and schema by @jeremyholtzman in #124
- @fivetran-joemarkiewicz made their first contribution in #83
- @Maayan-s made their first contribution in #77
- @GSokol made their first contribution in #76
- @erkanncelen made their first contribution in #115
- @jeremyholtzman made their first contribution in #124
Full Changelog: https://github.com/dbt-labs/dbt-codegen/compare/0.9.0...0.10.0
- Now uses
print
instead oflog
to output the generated text into the console. This enables you to invoke dbt with the--quiet
flag and directly pipe the codegen output into a new file, ending up with valid yaml
- @JorgenG (#86)
- Add support for including description placeholders for the source and table, which changes the behavior of
generate_source
wheninclude_descriptions
is set toTrue
. Previous logic only created description placeholders for the columns (#64, #66)
- Add optional
table_names
arg togenerate_source
(#50, #51) - Add support for importing descriptions from columns with the same names in upstream models. It is available by setting the parameter
upstream_descriptions
toTrue
ingenerate_model_yaml
(#61) - Added
case_sensitive_cols
argument togenerate_base_model
macro (#63) - Add optional
name
arg togenerate_source
(#64, #66)
- @rahulj51 (#51)
- @bodschut (#54)
- @b-per (#61)
- @graciegoheen (#63)
- @kbrock91 (#66)
This release creates breaking changes to the generate_source.sql
macro.
- add optional
table_pattern
argument togenerate_source.sql
macro. Default value is '%' to pull all tables in the raw data schema to preserve existing behavior if thetable_pattern
argument is not specified by the user.
This release supports any version (minor and patch) of v1, which means far less need for compatibility releases in the future.
- Change
require-dbt-version
to[">=1.0.0", "<2.0.0"]
- Bump dbt-utils dependency
- Replace
source-paths
anddata-paths
withmodel-paths
andseed-paths
respectively - Rename
data
andanalysis
directories toseeds
andanalyses
respectively - Replace
dbt_modules
withdbt_packages
inclean-targets
π¨ This is a compatibility release in preparation for dbt-core
v1.0.0 (π). Projects using this version with dbt-core
v1.0.x can expect to see a deprecation warning. This will be resolved in the next minor release.
- Requires
dbt>=0.20.0
anddbt-utils>=0.7.0
- Depends on
dbt-labs/dbt_utils
(instead offishtown-analytics/dbt_utils
)
- Add optional
leading_commas
arg togenerate_base_model
(#41 @jaypeedevlin) - Add optional
include_descriptions
arg togenerate_source
(#40 @djbelknapdbs)
- In the
generate_source
macro, usedbt_utils.get_relations_by_pattern
instead ofget_relations_by_prefix
, since the latter will be deprecated in the future (#42)
- Use new adapter.dispatch syntax (#44)
This is a quality of life release
- Fix rendering issues on hub.getdbt.com
- Fix integration tests due to python version compatibility
This is a bugfix release
- Use latest version of dbt-utils (0.6.2) to ensure generate_source_yaml works for non-target schemata (#34)
This release requires dbt v0.18.0, and dbt-utils v0.6.1. If you're not ready to upgrade, consider using a previous release of this package.
- Use dbt v0.18.0 (#31)
- Fix README rendering on hub (#32 @calvingiles)
The lower bound of dbt-utils
is now 0.4.0
.
This won't affect most users, since you're likely already using version of dbt-utils higher than this to achieve 0.17.0 compatibility.
- Change dbt-utils dependencies to
[>=0.4.0, <0.6.0]
(#29) - Fix tests (#29)
This package now requires dbt v0.17.x!
- Add
generate_model_yaml
(#18 @jtalmi)
- Update to v0.17.0, including
dbt_project.yml
version 2 syntax (#23) - Add GitHub templates and installation instructions (#23)
@marzaccaro made a PR for generate_model_yaml
, and, although I had reviewed it, I let the PR go stale and somehow completely forgot about it when merging PR #18 β this is completely my bad! So equal credit to @marzaccaro and @jtalmi for their work π
This is a bugfix release to improve compatibility with Snowflake
Bump utils version range
Small quality of life improvements
Initial release