[CT-1936] Support Google Cloud Auth from AWS Credentials File

[dbt-labs]

[CT-1936] Support Google Cloud Auth from AWS Credentials File

[McKnight-42]

@siephen going to open this issue up and would be more than happy to help in anyway i can.

[siephen]

@McKnight-42,

I'm thinking this would manifest as a new method that can be used called aws and it would use the following syntax to generate the credentials for the BigQuery Client from the AWS From File method.

Updating the following IF Block

Adding in the type here

Is this the right track?

[siephen]

@McKnight-42,

I'm thinking this would manifest as a new method that can be used called aws and it would use the following syntax to generate the credentials for the BigQuery Client from the AWS From File method.

Updating the following IF Block

Adding in the type here

Is this the right track?

@McKnight-42 Bumping my comment.

[McKnight-42]

@siephen so sorry for the late response; yes these the above are both spots you will need to add in some logic, may also need to add some new credentials specifically for aws connection here

dbt-bigquery/dbt/adapters/bigquery/connections.py

Line 89 in 072050e

class BigQueryCredentials(Credentials):

would love to see a draft pr on trying to get this to work and keep helping you build it out, already looking into what we might need to add it to CI/CD testing as well on our end.

[siephen]

@McKnight-42 , I drafted a PR for this here. I'm working through validating it on local with my internal team. Any initial thoughts? Also, where are the docs that will need to be updated for this new connection method option?

[McKnight-42]

@siephen fantastic! i'll pop over to the PR and leave some comments there when I can. as for docs updating i'd say this page https://docs.getdbt.com/reference/warehouse-profiles/bigquery-profile.

If you can I would appreciate any relevant information on what it takes to setup and get running locally yet? so we can test on our end as well to best assist?

[github-actions]

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please remove the stale label or comment on the issue, or it will be closed in 7 days.

[siephen]

@McKnight-42 , I have some questions over on the linked PR for this around how to write the test cases, can you take a look when you get a chance?

[github-actions]

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.

[github-actions]

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.