Hey team, I’m very pleased that

redshift-usage

statistics is added with this PR at v0.8.15. This connector requires Redshift Super User privileges to run this query with

svv_table_info

,

svl_user_info

tables and also explore other user queries. What’s the approach you follow to pass a Redshift super user to this connector? I’m not sure that data platform team allows us to use super user credentials in a connector. I guess, @witty-state-99511 can give better suggestions here 🙂

Hi @polite-flower-25924 are you concerned about putting the credentials inside the yml file?

yep. as plain-text.

the yml supports environment variables

ops, I didn’t know that string interpolation is supported through environment variables, I’m going to follow this approach. Thank you Shirshanka

My 2 cents: You should isolate DataHub metadata queries on redshift by creating a new

datahub_redshift_user

or something similar and granting

SYSLOG ACCESS UNRESTRICTED

that way you’re not using superuser account. Either way you should not store pwd in plaintext, but suggesting that you isolate datahub related queries that way you can measure the impact of these profile queries on your DB.

Thank you @quiet-kilobyte-82304 ! That’s a great suggestion. I’m going to let our data platform know about this method.