v0.8.3 dbt_asana

PR #39 includes the following updates:

Under the Hood

• Fixed asana__using_tags and asana__using_task_tags in the quickstart.yml configuration to ensure that, when their source tables are not selected, these variables are set to false and the below changes in v0.8.2 are applied in Quickstart.

Full Changelog: v0.8.2...v0.8.3

v0.8.2 dbt_asana

This release will introduce the following changes:

Feature Updates

• Introduces variables asana__using_tags and asana__using_task_tags to allow the tag and task_tag source tables to be disabled. By default, these variables are set to True. (#37)
• This will disable the tables int_asana__task_tags and asana__tag if either of the variables are set to False. This allows the downstream models to run even if the respective source tag and task_tag tables don't exist. (#37)
• This will exclude the fields tags and number_of_tags in asana__task if either of the variables are set to false.
• For more information on how to configure these variables, refer to the README. (#37)

Under the Hood

• Added asana__using_tags and asana__using_task_tags to the quickstart.yml configuration to ensure when these source tables are not selected, these variables are set to false and the above changes are applied in Quickstart. (#37)
• Added False configurations for asana__using_tags and asana__using_task_tags to our Buildkite run_models.sh script. (#37)
• Added consistency tests within integration_tests to ensure no unexpected row changes occur in the asana__tag and asana_task models in development. (#37)

Documentation

• Added Quickstart model counts to README. (#35)
• Corrected references to connectors and connections in the README. (#35)

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

v0.8.1 dbt_asana

PR #29 includes the following updates:

🎉 Feature Update 🎉

• Updated int_asana__task_projects to create the following new columns that are brought into asana__task. These new fields provide additional insight into your tasks.
  • project_ids
  • project_names
  • number_of_projects
• Note project_ids and project_names are aggregated lists of all ids/names associated with the task. You can parse or explode the items in the list using a comma + space (", ") as a delimiter. To keep the table grain at the task_id level, this list is not parsed by default.
  • See also our documentation.

Contributors

• @irvingpop (PR #25)

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

v0.8.0 dbt_asana

This release of dbt_asana incorporates the following changes:

🎉 Feature Update 🎉

• Databricks compatibility! (#28)

🚘 Under the Hood 🚘

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

dbt_asana v0.7.0

🚨 Breaking Changes 🚨:

PR #23 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 v0.6.0

Happy Monday! 👋

This release of dbt_asana package includes the following updates:

🛠 Deprecated columns fix 🛠

🚨 Breaking Changes 🚨

• As per our Release Notes for the Asana connector, we have updated the dbt_asana_source package to remove deprecated columns from the Task table - please refer to the June 2021 and March 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 #19 introduced the following updates.

• PostgreSQL compatibility
• Updated README for enhanced user experience

Contributors

@fivetran-poonamagate 21.

dbt_asana 0.5.0

🎉 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_asana_source. Additionally, the latest dbt_asana_source package has a dependency on the latest dbt_fivetran_utils. Further, 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.

Feature: Task Passthrough Columns

This release introduces new functionality -- the ability to add passthrough columns to the stg_asana__task table.

Learn more about how to implement this here.

Package Updates

🚨 This update introduces breaking changes: Output models are renamed to include a double underscore between the source name and the table name. For example, asana_team.sql is now asana__team.sql. Additionally, this release introduces custom schemas to output final models into a respective <target.schema>+_asana schema. Refer to the ReadMe for more details. 🚨

The release also:

• Introduces CircleCI testing
• Minor documentation updates