search

fivetran / dbt_mailchimp

Fivetran's Mailchimp dbt package
https://fivetran.github.io/dbt_mailchimp/
Apache License 2.0
3 stars 5 forks source link

FEATURE - Upgrade to align with Fivetran current package standards #20

Closed fivetran-joemarkiewicz closed 3 years ago

fivetran-joemarkiewicz commented 3 years ago

Are you a Fivetran customer?

Fivetran created Feature Request

Is your feature request related to a problem? Please describe.

No. This package currently works for users. However, we will want to upgrade this package to align with our current standard packages. Things that need to be updated within this package: - [ ] dbt_mailchimp_source creation and updates - [ ] CircleCi integration - [ ] Model naming convention changes (ie. mailchimp_automation_emails -> mailchimp__automation_emails) - [ ] Postgres and Databricks compatibility - [ ] Github Pages docs hosting **Describe the solution you'd like** Update the package to align with a Fivetran current standard package. Check [dbt_jira](https://github.com/fivetran/dbt_jira) for a reference. **Describe alternatives you've considered** No alternatives, this packages needs to be updated to match Fivetran current standards. **Additional context**

N/A

Please indicate the level of urgency and business impact of this request

Low - This does not need to be prioritized unless further requested by more users.

MarkMacArdle commented 3 years ago

Hi @fivetran-joemarkiewicz is there any work planned for this? I'd like to start using this package but would like to avoid dealing with name changes in the near future.

fivetran-joemarkiewicz commented 3 years ago

Hi @MarkMacArdle there actually are! We just got a new member to our team who will be tackling the upgrades next week! I will have her post back here once the upgrades are taking place. I also saw your post in dbt slack and will make sure to add an accommodation for this.

Thanks!

fivetran-reneeli commented 3 years ago

Hi @fivetran-joemarkiewicz is there any work planned for this? I'd like to start using this package but would like to avoid dealing with name changes in the near future.

Hi @MarkMacArdle, please check out our latest release of the Mailchimp package which brings the model up to date with current standards. We also changed segment to mailchimp_segment to avoid using the same variable name as other packages. Thanks for bringing that to our attention!