v0.9.0 dbt_asana_source

PR #41 includes the following updates:

Breaking Change for dbt Core < 1.9.6

Note: This is not relevant to Fivetran Quickstart users.

Migrated freshness from a top-level source property to a source config in alignment with recent updates from dbt Core. This will resolve the following deprecation warning that users running dbt >= 1.9.6 may have received:

[WARNING]: Deprecated functionality
Found `freshness` as a top-level property of `asana` in file
`models/src_asana.yml`. The `freshness` top-level property should be moved
into the `config` of `asana`.

IMPORTANT: Users running dbt Core < 1.9.6 will not be able to utilize freshness tests in this release or any subsequent releases, as older versions of dbt will not recognize freshness as a source config and therefore not run the tests.

If you are using dbt Core < 1.9.6 and want to continue running Asana freshness tests, please elect one of the following options:

1. (Recommended) Upgrade to dbt Core >= 1.9.6
2. Do not upgrade your installed version of the asana_source package. Pin your dependency on v0.8.2 in your packages.yml file.
3. Utilize a dbt override to overwrite the package's asana source and apply freshness via the previous release top-level property route. This will require you to copy and paste the entirety of the previous release src_asana.yml file and add an overrides: asana_source property.

Under the Hood

• Updates to ensure integration tests use latest version of dbt.

Full Changelog: v0.8.2...v0.9.0

v0.8.2 dbt_asana_source

This release includes the following updates:

Under the Hood

• Prepends materialized configs in the package's dbt_project.yml file with + to improve compatibility with the newer versions of dbt-core starting with v1.10.0. (PR #38)
• Updates the package maintainer pull request template. (PR #39)

Contributors

• @b-per (PR #38)

Full Changelog: v0.8.1...v0.8.2

v0.8.1 dbt_asana_source

This release introduces the following updates:

Feature Updates

• Introduces variables asana__using_tags and asana__using_task_tags to disable the stg_asana__tag and stg_asana__task_tag models respectively. This allows the downstream models to run even if the respective source tag and task_tag tables don't exist. (#37)
  • For more information on how to configure these variables, refer to the README.

Under the Hood

• Added False configurations for asana__using_tags and asana__using_task_tags to our Buildkite run_models.sh script. (#37)
• Updated src_asana.yml with the above variable configurations to the source tables tag and task_tag. (#37)

Documentation

• Corrected references to connectors and connections in the README. (#36)

Full Changelog: v0.8.0...v0.8.1

v0.8.0 dbt_asana_source

This release of dbt_asana_source incorporates the following changes:

🎉 Feature Update 🎉

• Databricks compatibility! (#30)

🚘 Under the Hood 🚘

• Incorporated the new fivetran_utils.drop_schemas_automation macro into the end of each Buildkite integration test job. (#28)
• Updated the pull request templates. (#28)

dbt_asana_source v0.7.0

🚨 Breaking Changes 🚨:

PR #27 includes the following breaking changes:

• Dispatch update for dbt-utils to dbt-core cross-db macros migration. Specifically {{ dbt_utils.<macro> }} have been updated to {{ dbt.<macro> }} for the below macros:
  • any_value
  • bool_or
  • cast_bool_to_text
  • concat
  • date_trunc
  • dateadd
  • datediff
  • escape_single_quotes
  • except
  • hash
  • intersect
  • last_day
  • length
  • listagg
  • position
  • replace
  • right
  • safe_cast
  • split_part
  • string_literal
  • type_bigint
  • type_float
  • type_int
  • type_numeric
  • type_string
  • type_timestamp
  • array_append
  • array_concat
  • array_construct
• For current_timestamp and current_timestamp_in_utc macros, the dispatch AND the macro names have been updated to the below, respectively:
  • dbt.current_timestamp_backcompat
  • dbt.current_timestamp_in_utc_backcompat
• dbt_utils.surrogate_key has also been updated to dbt_utils.generate_surrogate_key. Since the method for creating surrogate keys differ, we suggest all users do a full-refresh for the most accurate data. For more information, please refer to dbt-utils release notes for this update.
• Dependencies on fivetran/fivetran_utils have been upgraded, previously [">=0.3.0", "<0.4.0"] now [">=0.4.0", "<0.5.0"].

dbt_asana_source v0.6.0

Happy Monday!

This release of dbt_asana_source package includes the following updates:

🛠 Deprecated columns fix 🛠

🚨 Breaking Changes 🚨

• As per our Release Notes for the Asana connector, this new version of the package removes deprecated columns from the Task table (https://fivetran.com/docs/applications/asana/changelog#june2021) - please refer to the June 2021 and May 2021 release notes. The following columns have been deprecated from the Task table:
  • assignee_status
  • hearted - the liked column has been added to replace hearted
  • num_hearts - the num_likes column has been added to replace num_hearts
    Please be sure to update your queries.

🎉 Features 🎉

PR #24 introduced the following updates.

• PostgreSQL compatibility
• Updated README for enhanced user experience
• Add source identifiers to give users more dynamic flexibility

Contributors

• @fivetran-poonamagate (#21).

dbt_asana_source 0.5.1

🌮 Happy Tuesday! 🌮

Under the Hood

• Leveraged the {{ dbt_utils.type_timestamp() }} macro within the staging models for all timestamp fields.
  • This is needed as certain Redshift warehouses sync these fields as timestamptz by default which causes compilation errors in downstream models. This macro safely removes timezone values from the UTC timestamps and ensures success in downstream transformations.

Contributors

• @shreveasaurus (#18).

dbt_asana_source 0.5.0

Happy Monday!

🎉 dbt v1.0.0 Compatibility 🎉

🚨 Breaking Changes 🚨

• Adjusts the require-dbt-version to now be within the range [">=1.0.0", "<2.0.0"]. Additionally, the package has been updated for dbt v1.0.0 compatibility. If you are using a dbt version <1.0.0, you will need to upgrade in order to leverage the latest version of the package.
  • For help upgrading your package, I recommend reviewing this GitHub repo's Release Notes on what changes have been implemented since your last upgrade.
  • For help upgrading your dbt project to dbt v1.0.0, I recommend reviewing dbt-labs upgrading to 1.0.0 docs for more details on what changes must be made.
• Upgrades the package dependency to refer to the latest dbt_fivetran_utils. The latest dbt_fivetran_utils package also has a dependency on dbt_utils [">=0.8.0", "<0.9.0"].
  • Please note, if you are installing a version of dbt_utils in your packages.yml that is not in the range above then you will encounter a package dependency error.

dbt 0.20.0 Compatibility

🎉 dbt 0.20.0 Compatibility 🎉

🚨 This is a breaking change! 🚨 dbt v0.20.0 or greater is required for this release. If you are not ready to upgrade, consider using a previous release of this package.

Additional considerations when upgrading to this package:

• This package utilizes the latest v0.7.x release of the dbt-labls/dbt_utils package. If your project also utilizes a version of the fishtown-analytics/dbt_utils package then you will receive a duplicate package error. If this is the case you will need to consider upgrading your other packages to be compatible with this update or use a previous release of this package.
• Similar to the above point, all previous Fivetran dbt packages utilize the fishtown-analytics/dbt_utils package and you will need to upgrade all Fivetran dbt packages to the latest dbt 0.20.0 compatibility releases in order for your packages to run without package conflicts.

Fivetran Utils Dependency Update

🚧 Fivetran Utils Dependency Update 🚧

This release includes the following non-breaking changes:

• Update to the packages.yml to reference the recently released Fivetran Utils package. This is a necessary update to ensure this package is compatible with previous dbt releases before dbt v0.20.0 updates take place.