Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First of all, I'm super happy with DBT.
It's a great tool and it rids my team and I from the tedious and error-prone flow that we used to have before switching.
Since we're multiple people working on the same project, we need to align the access rights before creating new objects in our Postgres schemas.
Our current solution is to set two pre-hooks (one for models and one for seeds) that look like this:
This works ok, but your documentation states that it's possible to set a role in the dbt profile for Snowflake connections. I would like to be able to do that in Postgres as well.
This PR partially fixes #1955 as I haven't implemented the Redshift part of the issue. I'll do that when I get more familiar with Redshift if no one beats me to it.