-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
fix(snowflake): Allow encrypted_extra field to be imported #22357
fix(snowflake): Allow encrypted_extra field to be imported #22357
Conversation
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.
Congrats on making your first PR and thank you for contributing to Superset! 🎉 ❤️
We hope to see you in our Slack community too!
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.
This is great, @askldjd!
Codecov Report
@@ Coverage Diff @@
## master #22357 +/- ##
==========================================
- Coverage 66.85% 66.85% -0.01%
==========================================
Files 1847 1847
Lines 70560 70560
Branches 7737 7737
==========================================
- Hits 47173 47171 -2
- Misses 21380 21382 +2
Partials 2007 2007
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Is this fix only for Snowflake or also for BigQuery? I tried importing BiqQuery datasource with encrypted_extra field and importing is failing (Tried to import through the UI) |
SUMMARY
The
encrypted_extra
field holds the keypair to authenticate to Snowflake. However, this field can't be imported currently.See #22348.
TESTING INSTRUCTIONS
Here are my test steps:
where
$url
is the sqlachemy URL andencrypted_extra
is the JSON encoded JSON block. So it looks something like this:superset import_datasources -p snowflake-import.yaml
dbs
table and verify that both the UI entry and the imported entry are identical.Prior to the fix, step 4 would fail. The
encrypted_extra
column would be empty for the imported entry.ADDITIONAL INFORMATION
Fixes #22348