Further automating the staging model creation to prefill column fields in the final select statement.
**If this PR introduces a new macro, how did you test the new macro?**
To test new macro get_column_names_only, use
dbt run-operation get_column_names_only --args '{table_name: log, schema_name: fivetran_log, database_name: dbt-package-testing}' | tail -n +2 > fivetran_log/models/log__log_temp.sql
Then to test how the actual bash script generate_models gets updated, use
source dbt_packages/fivetran_utils/generate_models.sh '../dbt_fivetran_log_source' stg_fivetran_log dbt-package-testing fivetran_log log
If this PR introduces a modification to an existing macro, which packages is the macro currently present in and what steps were taken to test compatibility across packages?
Tested using fivetran log
Did you update the README to reflect the macro addition/modifications?
[x] Yes
[ ] No (provide further explanation)
Updated the readme with adding the new macro + updated affected macros
What change does this PR introduce?
Further automating the staging model creation to prefill column fields in the final select statement. **If this PR introduces a new macro, how did you test the new macro?**To test new macro
get_column_names_only, usedbt run-operation get_column_names_only --args '{table_name: log, schema_name: fivetran_log, database_name: dbt-package-testing}' | tail -n +2 > fivetran_log/models/log__log_temp.sqlThen to test how the actual bash script
generate_modelsgets updated, usesource dbt_packages/fivetran_utils/generate_models.sh '../dbt_fivetran_log_source' stg_fivetran_log dbt-package-testing fivetran_log logIf this PR introduces a modification to an existing macro, which packages is the macro currently present in and what steps were taken to test compatibility across packages?
Tested using fivetran log
Did you update the README to reflect the macro addition/modifications?
Updated the readme with adding the new macro + updated affected macros