Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug/add-disable-teams #32

Merged
merged 5 commits into from
Feb 7, 2023
Merged

bug/add-disable-teams #32

merged 5 commits into from
Feb 7, 2023

Conversation

fivetran-catfritz
Copy link
Contributor

@fivetran-catfritz fivetran-catfritz commented Jan 30, 2023

Are you a current Fivetran customer?

Fivetran PR

What change(s) does this PR introduce?

🚨 Breaking Change 🚨

  • Expanded the variable github__using_repo_team to also toggle on/off the TEAM table along with and in addition to the REPO_TEAM table. This was done to fix issues with dependent models in our transform package, where TEAM is only ever used in conjunction with REPO_TEAM. (#32)

🎉 PostgreSQL Compatibility 🎉

  • Tested and confirmed compatibility with postgres. (#32)

Did you update the CHANGELOG?

  • Yes

Does this PR introduce a breaking change?

  • Yes (please provide breaking change details below.)
  • No (please provide an explanation as to how the change is non-breaking below.)

Did you update the dbt_project.yml files with the version upgrade (please leverage standard semantic versioning)? (In both your main project and integration_tests)

  • Yes

Is this PR in response to a previously created Bug or Feature Request

How did you test the PR changes?

  • Buildkite
  • Local (please provide additional testing details below)

Select which warehouse(s) were used to test the PR

  • BigQuery
  • Redshift
  • Snowflake
  • Postgres
  • Databricks
  • Other (provide details below)

Provide an emoji that best describes your current mood

🌀

Feedback

We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your feedback on our existing dbt packages or what you'd like to see next.

Copy link
Contributor

@fivetran-sheringuyen fivetran-sheringuyen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @fivetran-catfritz ! Good job on this PR. I only left one minor suggestion in the CHANGELOG but otherwise, PR looks good an I have approved it.

CHANGELOG.md Outdated
## 🚨 Breaking Change 🚨
- Expanded the variable `github__using_repo_team` to also toggle on/off the `TEAM` table along with and in addition to the `REPO_TEAM` table. This was done to fix issues with dependent models in our transform package, where `TEAM` is only ever used in conjunction with `REPO_TEAM`. ([#32](https://github.com/fivetran/dbt_github_source/pull/32))

🎉 PostgreSQL Compatibility 🎉
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I recommend putting this into it's own subsection as it currently looks like this is under the Breaking Change section

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I have updated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] 'team' table seems to be optional [Feature] Add PostgreSQL support
2 participants