-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[#104] Ignore the Forbidden
exception in list_relations_without_caching
#108
Conversation
@McKnight-42 I don't understand the release cycle after separating |
@yu-iskw Hi sorry for not responding sooner, in regards to your CI question we have added a new env variable containing a second gcp to test against, currently working on making sure the integration tests will work properly. as for the release schedule now that adapters are separate. We are still working on the actual release schedule definition for when we will be doing patches. Thank you so much for working on this enhancement. |
@McKnight-42 Thank you for supporting me in #111 . I look forward to resolving the tests. If there is anything I can help, please let me know. |
@McKnight-42 I have resolved the conflicts in comparison with the default branch. I will look into #111 so that we enhance the unit tests. Many thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thank you for putting in the time on this.
@McKnight-42 It's my pleasure. Thank you for supporting me too. |
@McKnight-42 The CI jobs on the |
@yu-iskw Your good, these failures are due to different changes. |
…thout_caching` (dbt-labs#108) * [dbt-labs#104] Ignore the forbidden exception in `list_relations_without_caching` * Update CHANGELOG.md * Further update CHANGELOG.md Co-authored-by: Matthew McKnight <91097623+McKnight-42@users.noreply.github.com>
resolves #104
Description
When we would like to deal with partital dbt models as parts of all models with a service account to access the partital ones, dbt gets failed due to the lack of permissions for other models. So, we ignore the
google.api_core.exceptions.Forbidden
exception so that we skip errors because of the lack of permissions.By the way, how can we imlement unit tests for the update? I am not sure if we have multiple service accounts are available on the CI jobs.
Checklist
CHANGELOG.md
and added information about my change to the "dbt-bigquery next" section.What I tested
I used the repository to test the implementation, as I reported the issue #104.
https://github.com/yu-iskw/dbt-issue-with-multiple-service-accounts-on-bigquery
dbt compile
for partital resourcesdbt run
for partital resourcesdbt compile
for every resourcesdbt run
for every resources as expecteddbt executions with a tag to select a sub graph
dbt compile
passeddbt run
passeddbt executions with no model selection
dbt compile
dbt run
failed