[Bugfix] Add limit 0 to credits_used and usage_cost to fix Postgres errors

[fivetran-avinash]

PR Overview

This PR will address the following Issue/Feature: [#104]

This PR will result in the following new package version: 1.4.2

Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:

Bug Fixes

• Adjusted staging models stg_fivetran_platform__credits_used and stg_fivetran_platform__usage_cost to return empty tables if the respective fivetran_platform__credits_pricing and the fivetran_platform__usage_pricing variables for each model are disabled to avoid Postgres data type errors if those tables are null.

Under the Hood

• Added additional scripts to run_models.sh for the package with the variables fivetran_platform__credits_pricing set to false and fivetran_platform__usage_pricing set to true to recreate the error.
• Updated seed files to ensure downstream models properly populate into fivetran_platform__usage_mar_destination_history for validating this PR.

PR Checklist

Basic Validation

Please acknowledge that you have successfully performed the following commands locally:

• dbt run –full-refresh && dbt test
• [NA] 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, 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 share any and all of your validation steps:
See Height ticket

If you had to summarize this PR in an emoji, which would it be?

💳

[fivetran-joemarkiewicz]

@fivetran-avinash thanks for working through this! This is looking good, but I have a few comments and suggestions below. Let me know if you have any questions - we can sync on the SQL Server one in more detail next week, but you should be able to start building out the bones of a conditional knowing SQL Server likely doesn't support the limit function.

[fivetran-avinash]

@fivetran-joemarkiewicz Changes applied and ready for re-review.

[fivetran-joemarkiewicz]

@fivetran-avinash these changes look great to me, thanks for applying them! I have approved the PR as your changes look good, but I would like to hold off merging and releasing until we can get the sqlserver warehouse back up and running to fully test.

Once Buildkite is passing on the soon to be recreated sqlserver warehouse, we can initialize the release review process.

[fivetran-joemarkiewicz]

LGTM! With one suggestion in order to get BK passing.