Adding new packages soon to be released

[fivetran-joemarkiewicz]

Description

Adding the following new packages:

• Reddit Ads
  • A standard Fivetran ad reporting package that will be integrated into the Ad Reporting package as well
• Recharge
  • A new subscription platform dbt package that will help customers analyze data coming from the Recharge Fivetran connector.

Please note, these packages have not had an initial release at the moment. You can expect an official release in the next month. I just wanted to get ahead of the game to be prepared prior to the completion of the packages.

Link to your package's repository:

• https://github.com/fivetran/dbt_reddit_ads
• https://github.com/fivetran/dbt_reddit_ads_source
• https://github.com/fivetran/dbt_recharge
• https://github.com/fivetran/dbt_recharge_source

Checklist

This checklist is a cut down version of the best practices that we have identified as the package hub has grown. Although meeting these checklist items is not a prerequisite to being added to the Hub, we have found that packages which don't conform provide a worse user experience.

First run experience

• [X] The package includes a README which explains how to get started with the package and customise its behaviour
• [X] The README indicates which data warehouses/platforms are expected to work with this package

Customisability

• [X] The package uses ref or source, instead of hard-coding table references.

  Packages for data transformation (delete if not relevant):

• [X] provide a mechanism (such as variables) to customise the location of source tables.
• [X] do not assume database/schema names in sources.

Dependencies

Dependencies on dbt Core

• [X] The package has set a supported require-dbt-version range in dbt_project.yml. Example: A package which depends on functionality added in dbt Core 1.2 should set its require-dbt-version property to [">=1.2.0", "<2.0.0"].

  Dependencies on other packages defined in packages.yml:

• [X] Dependencies are imported from the dbt Package Hub when available, as opposed to a git installation.
• [X] Dependencies contain the widest possible range of supported versions, to minimise issues in dependency resolution.
• [X] In particular, dependencies are not pinned to a patch version unless there is a known incompatibility.

  Interoperability

• [X] The package does not override dbt Core behaviour in such a way as to impact other dbt resources (models, tests, etc) not provided by the package.
• [X] The package uses the cross-database macros built into dbt Core where available, such as {{ dbt.except() }} and {{ dbt.type_string() }}.
• [X] The package disambiguates its resource names to avoid clashes with nodes that are likely to already exist in a project. For example, packages should not provide a model simply called users.

Versioning

• [X] (Required): The package's git tags validates against the regex defined in version.py
• [X] The package's version follows the guidance of Semantic Versioning 2.0.0. (Note in particular the recommendation for production-ready packages to be version 1.0.0 or above)

[fivetran-joemarkiewicz]

Hey @dbeatty10! Correct, in the past nothing actually would show on the hub until we cut the initial release. Since none of these have been released yet, they will not show up. Unless something changed since the last PR of mine was merged 👀

[dbeatty10]

Perfect. Will be ready for you 🙌