-
Notifications
You must be signed in to change notification settings - Fork 155
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
Kms key encryption for seeds #193
Conversation
32c321a
to
e4ba036
Compare
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Julian.Frenzel.
|
d45b22f
to
59aaa46
Compare
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Julian.Frenzel.
|
59aaa46
to
949b946
Compare
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Julian.Frenzel.
|
949b946
to
7ecc17c
Compare
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Julian.Frenzel.
|
7ecc17c
to
e8c73d0
Compare
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Julian.Frenzel.
|
e8c73d0
to
92d6a57
Compare
92d6a57
to
6c79aa5
Compare
@@ -10,8 +10,9 @@ | |||
{% macro bigquery__load_csv_rows(model, agate_table) %} | |||
|
|||
{%- set column_override = model['config'].get('column_types', {}) -%} | |||
{%- set kms_key_name = model['config'].get('kms_key_name', {}) -%} |
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.
I think the data type of kms_key_name
is str
. If so, does {}
make sense as the default here? Is the expected arg datatype on EncryptionConfiguration
str
or dict
?
from google.cloud import bigquery | ||
from google.cloud import kms | ||
|
||
from tests.integration.base import DBTIntegrationTest, use_profile |
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.
We've moved away from the tests in tests/integration
towards tests/functional
. They are testing the same functionality, but use a new framework. One of the changes is that we moved from unittest
to pytest
. Could you migrate these tests to the new framework? At a cursory glance, I think you'd need to make these changes:
GcpKmsAdapter
- looks like it would move over as-is
TestSimpleSeedKmsKeyName
- you could probably jetison
schema
andproject_id
in favor of theupdate_project_config()
fixture setUp
would need to be apytest
fixture withautouse=True
- you could probably jetison
TestSimpleSeedKmsKeyNameBq
- you'd need to find a new source for
biqguery_profile()
; I'm not that familiar with it, but I'm sure that's done in other tests intests/functional
- you'd need to find a new source for
Closing due to lack of engagement. |
resolves #191
Description
Support kms_key_name feature for seed data.
The integration test adds a kms, which can not be deleted. The testing service account needs the role "Cloud KMS Admin" to create the key. The hard part of the PR is the integration test. Please let me know, if this fits your quality requirements.
Checklist
CHANGELOG.md
and added information about my change to the "dbt-bigquery next" section.