diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
index 17c2c54..38c56bc 100644
--- a/.github/ISSUE_TEMPLATE/bug-report.yml
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -1,7 +1,7 @@
name: š Bug
description: Report a bug or an issue you've found within the dbt package
title: "[Bug]
"
-labels: ["bug", "triage"]
+labels: ["type:bug"]
body:
- type: markdown
attributes:
@@ -35,6 +35,12 @@ body:
description: A concise description of what you expected to happen.
validations:
required: true
+ - type: textarea
+ attributes:
+ label: Possible solution
+ description: Were you able to investigate and/or discover a potential fix to this bug in your investigation? If so, it would be much appreciated if you could submit code samples to show us how your fix resolved this issue.
+ validations:
+ required: false
- type: textarea
attributes:
label: dbt Project configurations
@@ -61,6 +67,19 @@ body:
- other (mention it in "Additional Context")
validations:
required: true
+ - type: dropdown
+ id: orchestration_type
+ attributes:
+ label: How are you running this dbt package?
+ multiple: true
+ options:
+ - Fivetran Quickstart Data Model
+ - Fivetran Transformations
+ - dbt Coreā¢
+ - dbt Cloudā¢
+ - other (mention it in "Additional Context")
+ validations:
+ required: true
- type: textarea
attributes:
label: dbt Version
@@ -83,6 +102,6 @@ body:
description: Our team will assess this issue and let you know if we will add it to a future sprint. However, if you would like to expedite the solution, we encourage you to contribute to the package via a PR. Our team will then work with you to approve and merge your contributions as soon as possible.
options:
- label: Yes.
- - label: Yes, but I will need assistance and will schedule time during our [office hours](https://calendly.com/fivetran-solutions-team/fivetran-solutions-team-office-hours) for guidance
+ - label: Yes, but I will need assistance.
- label: No.
required: false
\ No newline at end of file
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
index 65a074b..496b3bd 100644
--- a/.github/ISSUE_TEMPLATE/config.yml
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -1,7 +1,7 @@
contact_links:
- - name: Ask a question during our office hours
- url: https://calendly.com/fivetran-solutions-team/fivetran-solutions-team-office-hours
- about: Schedule time during the external office hours block with the Fivetran Analytics Engineering team for support
+ - name: Provide feedback to our dbt package team
+ url: https://www.surveymonkey.com/r/DQ7K7WW
+ about: Fill out our survey form to provide valuable feedback to the Fivetran team developing and maintaining the dbt packages.
- name: Fivetran connector question
url: https://support.fivetran.com/hc
about: Have a question about your connector? Check out the Fivetran support portal for more details.
@@ -10,4 +10,4 @@ contact_links:
about: Check out the dbt docs for all dbt related information
- name: Hang out in dbt Slack
url: https://www.getdbt.com/community/
- about: Have a question or just want to chat with fellow data friends, join dbt Slack and hangout in the tools-fivetran channel with us!
\ No newline at end of file
+ about: Have a question or just want to chat with fellow data friends, join dbt Slack and hangout in the tools-fivetran channel with us!
diff --git a/.github/ISSUE_TEMPLATE/feature-request.yml b/.github/ISSUE_TEMPLATE/feature-request.yml
index a1d28bb..529e9bc 100644
--- a/.github/ISSUE_TEMPLATE/feature-request.yml
+++ b/.github/ISSUE_TEMPLATE/feature-request.yml
@@ -1,7 +1,7 @@
name: š Feature
description: Suggest a new feature for the Fivetran dbt package
title: "[Feature] "
-labels: ["enhancement"]
+labels: ["type:enhancement"]
body:
- type: markdown
attributes:
@@ -20,6 +20,13 @@ body:
description: A clear and concise description of what you want to happen and why you want the new feature.
validations:
required: true
+ - type: textarea
+ attributes:
+ label: How would you implement this feature?
+ description: |
+ How would you build out this feature with your existing data? Any code examples you can provide to help accelerate development on this issue?
+ validations:
+ required: true
- type: textarea
attributes:
label: Describe alternatives you've considered
@@ -34,7 +41,7 @@ body:
description: Our team will assess this feature and let you know if we will add it to a future sprint. However, if you would like to expedite the feature, we encourage you to contribute to the package via a PR. Our team will then work with you to approve and merge your contributions as soon as possible.
options:
- label: Yes.
- - label: Yes, but I will need assistance and will schedule time during your [office hours](https://calendly.com/fivetran-solutions-team/fivetran-solutions-team-office-hours) for guidance.
+ - label: Yes, but I will need assistance.
- label: No.
required: false
- type: textarea
diff --git a/.github/PULL_REQUEST_TEMPLATE/maintainer_pull_request_template.md b/.github/PULL_REQUEST_TEMPLATE/maintainer_pull_request_template.md
index 768ac3f..3220674 100644
--- a/.github/PULL_REQUEST_TEMPLATE/maintainer_pull_request_template.md
+++ b/.github/PULL_REQUEST_TEMPLATE/maintainer_pull_request_template.md
@@ -4,48 +4,26 @@
**This PR will result in the following new package version:**
-**Please detail what change(s) this PR introduces and any additional information that should be known during the review of this PR:**
+**Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:**
+
## PR Checklist
### Basic Validation
Please acknowledge that you have successfully performed the following commands locally:
-- [ ] dbt compile
-- [ ] dbt run āfull-refresh
-- [ ] dbt run
-- [ ] dbt test
-- [ ] dbt run āvars (if applicable)
+- [ ] dbt run āfull-refresh && dbt test
+- [ ] dbt run (if incremental models are present) && dbt test
Before marking this PR as "ready for review" the following have been applied:
-- [ ] The appropriate issue has been linked and tagged
-- [ ] You are assigned to the corresponding issue and this PR
+- [ ] The appropriate issue has been linked, tagged, and properly assigned
+- [ ] All necessary documentation and version upgrades have been applied
+- [ ] docs were regenerated (unless this PR does not include any code or yml updates)
- [ ] BuildKite integration tests are passing
+- [ ] Detailed validation steps have been provided below
### Detailed Validation
-Please acknowledge that the following validation checks have been performed prior to marking this PR as "ready for review":
-- [ ] You have validated these changes and assure this PR will address the respective Issue/Feature.
-- [ ] You are reasonably confident these changes will not impact any other components of this package or any dependent packages.
-- [ ] You have provided details below around the validation steps performed to gain confidence in these changes.
+Please share any and all of your validation steps:
-### Standard Updates
-Please acknowledge that your PR contains the following standard updates:
-- Package versioning has been appropriately indexed in the following locations:
- - [ ] indexed within dbt_project.yml
- - [ ] indexed within integration_tests/dbt_project.yml
-- [ ] CHANGELOG has individual entries for each respective change in this PR
-
-- [ ] README updates have been applied (if applicable)
-
-- [ ] DECISIONLOG updates have been updated (if applicable)
-- [ ] Appropriate yml documentation has been added (if applicable)
-
-### dbt Docs
-Please acknowledge that after the above were all completed the below were applied to your branch:
-- [ ] docs were regenerated (unless this PR does not include any code or yml updates)
-
### If you had to summarize this PR in an emoji, which would it be?
-:dancer:
+:dancer:
\ No newline at end of file
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index b4e7e8e..30849fd 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -19,7 +19,13 @@
- [ ] Yes
-**Provide an emoji that best describes your current mood**
+**Typically there are additional maintenance changes required before this will be ready for an upcoming release. Are you comfortable with the Fivetran team making a few commits directly to your branch?**
+
+
+- [ ] Yes
+- [ ] No
+
+**If you had to summarize this PR in an emoji, which would it be?**
:dancer:
diff --git a/.github/workflows/auto-release.yml b/.github/workflows/auto-release.yml
new file mode 100644
index 0000000..8ed5853
--- /dev/null
+++ b/.github/workflows/auto-release.yml
@@ -0,0 +1,13 @@
+name: 'auto release'
+on:
+ pull_request:
+ types:
+ - closed
+ branches:
+ - main
+
+jobs:
+ call-workflow-passing-data:
+ if: github.event.pull_request.merged
+ uses: fivetran/dbt_package_automations/.github/workflows/auto-release.yml@main
+ secrets: inherit
\ No newline at end of file
diff --git a/README.md b/README.md
index 4a21051..54a1159 100644
--- a/README.md
+++ b/README.md
@@ -11,7 +11,7 @@
# Amazon Ads Source dbt Package ([Docs](https://fivetran.github.io/dbt_amazon_ads_source/))
-# š£ What does this dbt package do?
+## What does this dbt package do?
- Materializes [Amazon Ads staging tables](https://fivetran.github.io/dbt_amazon_ads_source/#!/overview/amazon_ads_source/models/?g_v=1&g_e=seeds), which leverage data in the format described by [this ERD](https://fivetran.com/docs/applications/amazon-ads#schemainformation). These staging tables clean, test, and prepare your Amazon Ads data from [Fivetran's connector](https://fivetran.com/docs/applications/amazon-ads) for analysis by doing the following:
- Names columns for consistency across all packages and for easier analysis
- Adds freshness tests to source data
@@ -19,14 +19,14 @@
- Generates a comprehensive data dictionary of your Amazon Ads data through the [dbt docs site](https://fivetran.github.io/dbt_amazon_ads_source/).
- These tables are designed to work simultaneously with our [Amazon Ads transformation package](https://github.com/fivetran/dbt_amazon_ads).
-# šÆ How do I use the dbt package?
-## Step 1: Prerequisites
+## How do I use the dbt package?
+### Step 1: Prerequisites
To use this dbt package, you must have the following:
- At least one Fivetran Amazon_ads connector syncing data into your destination.
- A **BigQuery**, **Snowflake**, **Redshift**, **PostgreSQL**, or **Databricks** destination.
-## Step 2: Install the package (skip if also using the `amazon_ads` transformation package)
+### Step 2: Install the package (skip if also using the `amazon_ads` transformation package)
If you are **not** using the [Amazon Ads transformation package](https://github.com/fivetran/dbt_amazon_ads), include the following `amazon_ads_source` package version in your `packages.yml` file.
> TIP: Check [dbt Hub](https://hub.getdbt.com/) for the latest installation instructions, or [read dbt's Package Management documentation](https://docs.getdbt.com/docs/package-management) for more information on installing packages.
```yaml
@@ -35,7 +35,7 @@ packages:
version: [">=0.3.0", "<0.4.0"] # we recommend using ranges to capture non-breaking changes automatically
```
-## Step 3: Define database and schema variables
+### Step 3: Define database and schema variables
By default, this package runs using your destination and the `amazon_ads` schema. If this is not where your Amazon_ads data is (for example, if your Amazon_ads schema is named `amazon_ads_fivetran`), add the following configuration to your root `dbt_project.yml` file:
```yml
@@ -44,7 +44,7 @@ vars:
amazon_ads_schema: your_schema_name
```
-## Step 4: Disable models for non-existent sources
+### Step 4: Disable models for non-existent sources
Your Amazon Ads connector may not sync every table that this package expects. If you do not have the `PORTFOLIO_HISTORY` table synced, add the following variable to your root `dbt_project.yml` file:
```yml
@@ -52,8 +52,8 @@ vars:
amazon_ads__portfolio_history_enabled: False # Disable if you do not have the portfolio table. Default is True.
```
-## (Optional) Step 5: Additional configurations
-### Union multiple connectors
+### (Optional) Step 5: Additional configurations
+#### Union multiple connectors
If you have multiple amazon_ads connectors in Fivetran and would like to use this package on all of them simultaneously, we have provided functionality to do so. The package will union all of the data together and pass the unioned table into the transformations. You will be able to see which source it came from in the `source_relation` column of each model. To use this functionality, you will need to set either the `amazon_ads_union_schemas` OR `amazon_ads_union_databases` variables (cannot do both) in your root `dbt_project.yml` file:
```yml
@@ -61,11 +61,11 @@ vars:
amazon_ads_union_schemas: ['amazon_ads_usa','amazon_ads_canada'] # use this if the data is in different schemas/datasets of the same database/project
amazon_ads_union_databases: ['amazon_ads_usa','amazon_ads_canada'] # use this if the data is in different databases/projects but uses the same schema name
```
-Please be aware that the native `source.yml` connection set up in the package will not function when the union schema/database feature is utilized. Although the data will be correctly combined, you will not observe the sources linked to the package models in the Directed Acyclic Graph (DAG). This happens because the package includes only one defined `source.yml`.
+> NOTE: The native `source.yml` connection set up in the package will not function when the union schema/database feature is utilized. Although the data will be correctly combined, you will not observe the sources linked to the package models in the Directed Acyclic Graph (DAG). This happens because the package includes only one defined `source.yml`.
To connect your multiple schema/database sources to the package models, follow the steps outlined in the [Union Data Defined Sources Configuration](https://github.com/fivetran/dbt_fivetran_utils/tree/releases/v0.4.latest#union_data-source) section of the Fivetran Utils documentation for the union_data macro. This will ensure a proper configuration and correct visualization of connections in the DAG.
-### Passing Through Additional Metrics
+#### Passing Through Additional Metrics
By default, this package will select `clicks`, `impressions`, and `cost` from the source reporting tables to store into the staging models. If you would like to pass through additional metrics to the staging models, add the following configurations to your `dbt_project.yml` file. These variables allow the pass-through fields to be aliased (`alias`) if desired, but not required. Use the following format for declaring the respective pass-through variables:
> **Note** Ensure you exercised due diligence when adding metrics to these models. The metrics added by default (clicks, impressions, and cost) have been vetted by the Fivetran team maintaining this package for accuracy. There are metrics included within the source reports, for example, metric averages, which may be inaccurately represented at the grain for reports created in this package. You want to ensure whichever metrics you pass through are indeed appropriate to aggregate at the respective reporting levels provided in this package.
@@ -89,7 +89,7 @@ vars:
alias: "field_id"
```
-### Changing the Build Schema
+#### Changing the Build Schema
By default, this package will build the Amazon_ads staging models within a schema titled ( + `amazon_ads_source`) in your destination. If this is not where you would like your Amazon Ads staging data to be written, add the following configuration to your root `dbt_project.yml` file:
```yml
@@ -98,7 +98,7 @@ models:
+schema: my_new_schema_name # leave blank for just the target_schema
```
-### Change the source table references
+#### Change the source table references
If an individual source table has a different name than the package expects, add the table name as it appears in your destination to the respective variable:
> IMPORTANT: See this project's [`dbt_project.yml`](https://github.com/fivetran/dbt_amazon_ads_source/blob/main/dbt_project.yml) variable declarations to see the expected names.
@@ -108,14 +108,14 @@ vars:
amazon_ads__identifier: your_table_name
```
-## (Optional) Step 6: Orchestrate your models with Fivetran Transformations for dbt Coreā¢
+### (Optional) Step 6: Orchestrate your models with Fivetran Transformations for dbt Coreā¢
Expand for more details
Fivetran offers the ability for you to orchestrate your dbt project through [Fivetran Transformations for dbt Coreā¢](https://fivetran.com/docs/transformations/dbt). Learn how to set up your project for orchestration through Fivetran in our [Transformations for dbt Coreā¢ setup guides](https://fivetran.com/docs/transformations/dbt#setupguide).
-# š Does this package have dependencies?
+## Does this package have dependencies?
This dbt package is dependent on the following dbt packages. Be aware that these dependencies are installed by default within this package. For more information on the following packages, refer to the [dbt hub](https://hub.getdbt.com/) site.
> IMPORTANT: If you have any of these dependent packages in your own `packages.yml` file, we highly recommend that you remove them from your root `packages.yml` to avoid package version conflicts.
```yml
@@ -126,16 +126,15 @@ packages:
- package: dbt-labs/dbt_utils
version: [">=1.0.0", "<2.0.0"]
```
-# š How is this package maintained and can I contribute?
-## Package Maintenance
+## How is this package maintained and can I contribute?
+### Package Maintenance
The Fivetran team maintaining this package _only_ maintains the latest version of the package. We highly recommend that you stay consistent with the [latest version](https://hub.getdbt.com/fivetran/amazon_ads_source/latest/) of the package and refer to the [CHANGELOG](https://github.com/fivetran/dbt_amazon_ads_source/blob/main/CHANGELOG.md) and release notes for more information on changes across versions.
-## Contributions
-A small team of analytics engineers at Fivetran develops these dbt packages. However, the packages are made better by community contributions!
+### Contributions
+A small team of analytics engineers at Fivetran develops these dbt packages. However, the packages are made better by community contributions.
-We highly encourage and welcome contributions to this package. Check out [this dbt Discourse article](https://discourse.getdbt.com/t/contributing-to-a-dbt-package/657) to learn how to contribute to a dbt package!
+We highly encourage and welcome contributions to this package. Check out [this dbt Discourse article](https://discourse.getdbt.com/t/contributing-to-a-dbt-package/657) to learn how to contribute to a dbt package.
-# šŖ Are there any resources available?
-- If you have questions or want to reach out for help, refer to the [GitHub Issue](https://github.com/fivetran/dbt_amazon_ads_source/issues/new/choose) section to find the right avenue of support for you.
+## Are there any resources available?
+- If you have questions or want to reach out for help, see the [GitHub Issue](https://github.com/fivetran/dbt_amazon_ads_source/issues/new/choose) section to find the right avenue of support for you.
- If you would like to provide feedback to the dbt package team at Fivetran or would like to request a new dbt package, fill out our [Feedback Form](https://www.surveymonkey.com/r/DQ7K7WW).
-- Have questions or just want to say hi? Book a time during our office hours [on Calendly](https://calendly.com/fivetran-solutions-team/fivetran-solutions-team-office-hours) or email us at solutions@fivetran.com.