You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the tutorial, users may use the SECURE EXTRA field to supply a Key Pair as authentication. However, it is not clear how this can be done when the datasources are configured through YAML.
I was able to configure the database manually through the UI. However, when I tried to export the same database, the keypair field does not exist. Looking over the codebase, the import seems to suggest that it should be a field called encrypted_extra.
I tried to supply the encrypted_extra field in the datasource yaml, but the field didn't seem to make it (as indicated by the logs). Any guidance would be greatly appreciated.
Make sure to follow these steps before submitting your issue - thank you!
[ *] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[* ] I have reproduced the issue with at least the latest released version of superset.
[ *] I have checked the issue tracker for the same issue and I haven't found one similar.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
How to reproduce the bug
In the tutorial, users may use the
SECURE EXTRA
field to supply a Key Pair as authentication. However, it is not clear how this can be done when the datasources are configured through YAML.I was able to configure the database manually through the UI. However, when I tried to export the same database, the keypair field does not exist. Looking over the codebase, the import seems to suggest that it should be a field called encrypted_extra.
I tried to supply the
encrypted_extra
field in the datasource yaml, but the field didn't seem to make it (as indicated by the logs). Any guidance would be greatly appreciated.Make sure to follow these steps before submitting your issue - thank you!
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: