Add UI-only database configuration method for extended authorization scenarios#8448
Merged
dpgaspar merged 9 commits intoapache:masterfrom Oct 28, 2019
Merged
Conversation
added 2 commits
October 24, 2019 13:31
mistercrunch
approved these changes
Oct 24, 2019
| "impersonate_user", | ||
| "allow_multi_schema_metadata_fetch", | ||
| "extra", | ||
| "encrypted_extra", |
Member
There was a problem hiding this comment.
I just confirmed that this doesn't show in show_columns
mistercrunch
approved these changes
Oct 25, 2019
villebro
approved these changes
Oct 25, 2019
dpgaspar
reviewed
Oct 25, 2019
dpgaspar
reviewed
Oct 25, 2019
Codecov Report
@@ Coverage Diff @@
## master #8448 +/- ##
==========================================
- Coverage 67.61% 66.57% -1.04%
==========================================
Files 448 448
Lines 22486 22509 +23
Branches 2364 2364
==========================================
- Hits 15204 14986 -218
- Misses 7144 7385 +241
Partials 138 138
Continue to review full report at Codecov.
|
dpgaspar
approved these changes
Oct 28, 2019
12 tasks
graceguo-supercat
pushed a commit
that referenced
this pull request
Nov 13, 2019
…scenarios (#8448) * Add encrypted_extra to dbs * WIP - UI-based BigQuery connection configuration * Fix 500 bubbling to the surface when adding a database connection * Add check for valid json * black formatting: * isort * Incorporate PR feedback. Thanks all! * black * Typo fix in CONTRIBUTING.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
CATEGORY
Choose one
SUMMARY
Problem statement: currently connections to BigQuery databases cannot be configured without adding code to Superset or adding configuration to its execution environment in the form of Google Cloud account credentials.
Solution proposed: Add an encrypted field on the
dbstable to hold extended connection information. This field can hold JSON configuration including secrets and add that information on to the database connection object during instantiation. This allows us to configure a service account in Google Cloud and connect to a BigQuery dataset without any code or configuration changes in Superset.BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TEST PLAN
Add Databasescreen in Supersetbigquery://project-namewhereproject-nameis the name of the Google Cloud project that your BigQuery dataset is associated with.Secure Extrafield with the following structure:{ "credentials_info": <content from the identity file from Google Cloud> }ADDITIONAL INFORMATION
REVIEWERS
@mistercrunch @dpgaspar