update/twitter-organic-source-change (#11)

* update/twitter-organic-source-change

* docs regen

* Update CHANGELOG.md

* Apply suggestions from code review

Co-authored-by: Avinash Kunnath <[email protected]>

* Update packages.yml

---------

Co-authored-by: Avinash Kunnath <[email protected]>

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -83,6 +83,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

.github/ISSUE_TEMPLATE/config.yml

@@ -1,7 +1,4 @@
 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: 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.

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -34,7 +34,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

.github/PULL_REQUEST_TEMPLATE/maintainer_pull_request_template.md

@@ -16,6 +16,7 @@ Please acknowledge that you have successfully performed the following commands l
 Before marking this PR as "ready for review" the following have been applied:
 - [ ] The appropriate issue has been linked, tagged, and properly assigned
 - [ ] All necessary documentation and version upgrades have been applied
+    <!--- Be sure to update the package version in the dbt_project.yml, integration_tests/dbt_project.yml, and README if necessary. -->
 - [ ] 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

.github/pull_request_template.md

@@ -30,4 +30,4 @@ We are so excited you decided to contribute to the Fivetran community dbt packag
 **PR Template** 
 - [Community Pull Request Template](?expand=1&template=pull_request_template.md) (default)
 
-- [Maintainer Pull Request Template](?expand=1&template=maintainer_pull_request_template.md) (to be used by maintainers)
+- [Maintainer Pull Request Template](?expand=1&template=maintainer_pull_request_template.md) (to be used by maintainers)

.gitignore

@@ -5,4 +5,6 @@ dbt_packages/
 logs/
 venv/
 .DS_Store
-dbt_packages/
+dbt_packages/
+env/
+pacakge-lock.yml

CHANGELOG.md

@@ -1,7 +1,35 @@
-# dbt_social_media_reporting vNEXTRELEASE
+# dbt_social_media_reporting v0.5.0
+
+## Upstream Breaking Changes (Twitter Organic)
+[PR #12](https://github.com/fivetran/dbt_twitter_organic_source/pull/12) from the upstream `dbt_twitter_organic_source` package includes the following breaking change updates:
+
+- The source defined in the `src_twitter_organic.yml` file has been renamed from `twitter_organic` to `twitter` to align with the default schema name used by the upstream Fivetran connector.
+    - If you're referencing sources from the upstream Twitter Organic packages, please update your source references as needed. See below for the full scope of source changes.
+
+| **New Source Reference** | **Old Source Reference** |
+|----------------------------------|----------------------------------|
+| `"{{ source('twitter','account_history') }}"` | `"{{ source('twitter_organic','account_history') }}"` |
+| `"{{ source('twitter','organic_tweet_report') }}"` | `"{{ source('twitter_organic','organic_tweet_report') }}"` |
+| `"{{ source('twitter','tweet') }}"` | `"{{ source('twitter_organic','tweet') }}"` |
+| `"{{ source('twitter','twitter_user_history') }}"` | `"{{ source('twitter_organic','twitter_user_history') }}"` |
+
+- The default schema name has been modified from `twitter_organic` to now be `twitter` to more closely align with the default schema name generated by the Fivetran connector. Please be aware if you were leveraging the previous default schema then you will need to update the `twitter_organic_schema` variable accordingly. 
+- All identifier variables in the `src_twitter_organic.yml` file have been renamed. If you’re using any of these in your project, please update them accordingly. The changes include: 
+    - Prepending `twitter_organic_*` has been updated to `twitter_*` to align with the schema change.
+    - The spelling of `*_identifer` has been corrected to `*_identifier`.
+
+| **New Identifier Variable Name** | **Old Identifier Variable Name** |
+|----------------------------------|----------------------------------|
+| `twitter_account_history_identifier` | `twitter_organic_account_history_identifer` |
+| `twitter_organic_tweet_report_identifier` | `twitter_organic_organic_tweet_report_identifer` |
+| `twitter_tweet_identifier` | `twitter_organic_tweet_identifer` |
+| `twitter_twitter_user_history_identifier` | `twitter_organic_twitter_user_history_identifer` |
 
 ## Under the Hood
-- Addition of a section tag within the README so the model descriptions may be accessible within the Fivetran UI for Quickstart.
+- Consistency validation for integration tests has been added for the `social_media_reporting__rollup_report` model. ([PR #11](https://github.com/fivetran/dbt_social_media_reporting/pull/11))
+- Updated the maintainer PR, Issue, Feature Request, and Config templates to resemble the most up to date format. ([PR #11](https://github.com/fivetran/dbt_social_media_reporting/pull/11))
+- Renamed the Twitter Organic seed files to allow for more testing functionality. ([PR #11](https://github.com/fivetran/dbt_social_media_reporting/pull/11))
+- Addition of a section tag within the README so the model descriptions may be accessible within the Fivetran UI for Quickstart. ([PR #10](https://github.com/fivetran/dbt_social_media_reporting/pull/10))
 
 # dbt_social_media_reporting v0.4.0
 [PR #8](https://github.com/fivetran/dbt_social_media_reporting/pull/8) includes the following breaking changes:

README.md

@@ -59,7 +59,7 @@ Include the following github package version in your `packages.yml`
 ```yaml
 packages:
   - package: fivetran/social_media_reporting
-    version: [">=0.3.0", "<0.4.0"] # we recommend using ranges to capture non-breaking changes automatically
+    version: [">=0.5.0", "<0.6.0"] # we recommend using ranges to capture non-breaking changes automatically
 ```
 Do NOT include the upstream social media packages in this file. The transformation package itself has a dependency on it and will install the upstream packages as well.
 
@@ -178,10 +178,10 @@ packages:
       version: [">=0.2.0", "<0.3.0"]
 
     - package: fivetran/twitter_organic
-      version: [">=0.2.0", "<0.3.0"]
+      version: [">=0.3.0", "<0.4.0"]
 
     - package: fivetran/twitter_organic_source
-      version: [">=0.2.0", "<0.3.0"]
+      version: [">=0.3.0", "<0.4.0"]
 
     - package: fivetran/linkedin_pages
       version: [">=0.3.0", "<0.4.0"]
@@ -211,4 +211,3 @@ We highly encourage and welcome contributions to this package. Check out [this p
 # 🏪 Are there any resources available?
 - If you encounter any questions or want to reach out for help, please refer to the [GitHub Issue](https://github.com/fivetran/dbt_social_media_reporting/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 future dbt package to be developed, then feel free to fill out our [Feedback Form](https://www.surveymonkey.com/r/DQ7K7WW).
-- Have questions or want to just say hi? Book a time during our office hours [here](https://calendly.com/fivetran-solutions-team/fivetran-solutions-team-office-hours) or send us an email at [email protected].

dbt_project.yml

@@ -1,5 +1,5 @@
 name: 'social_media_reporting'
-version: '0.3.0'
+version: '0.5.0'
 config-version: 2
 require-dbt-version: [">=1.3.0", "<2.0.0"]
 vars: