By default, the schema name for the pharmacy models is generated as
"
pharmacy__...."
Normally its not an issue but when integrating with dagster or external tools that have validations on schema names, this throws an error that the schema name is invalid.
How has this been tested?
Executed the build and deployed the datamart in postgres.
Reviewer focus
Please summarize the specific items you’d like the reviewer(s) to look into.
any test cases you might need to integrate this into the code base
Checklist before requesting a review
[ ] I have added at least one Github label to this PR (bug, enhancement, breaking change,...)
Describe your changes
By default, the schema name for the pharmacy models is generated as
Normally its not an issue but when integrating with dagster or external tools that have validations on schema names, this throws an error that the schema name is invalid.
How has this been tested?
Executed the build and deployed the datamart in postgres.
Reviewer focus
Please summarize the specific items you’d like the reviewer(s) to look into.
Checklist before requesting a review
tuva_last_run
to the final outputPackage release checklist
dbt_project.yml
(Optional) Gif of how this PR makes you feel
Loom link