Have 100+ data sources in Quick with Snowflake as the source. Inexplicably after creating the data sources we can no longer see what Snowflake user is tied to the data source, i.e. if we create a data source connecting to a Snowflake user MY_SNOWFLAKE_USER we can never again figure out that user was used for the data source. We cannot do this manually by 'edit’ing the data source, where it shows the SNowflake URL, etc. but NOT the username, nor does the AWS CLI return the username despite again showing other aspects of the connection. This makes it impossible to audit or mitigate changes to the snowflake user, for instance if we want to add/remove permissions from that user or see where that user is being used.
Yes a tiny bit of this can be done from the Snowflake side via auditing connections but this is kind of ridiculous. Why doesn’t Quick let us see the DB username associated with a data source.
Hi @ngil and welcome to the community!
As far as I can tell, this is by design (credentials are stored securely and not surfaced back), but I agree it creates a real gap for auditing and managing which service accounts are tied to which data sources. Since you’ve already tagged this as a ‘feature-request,’ I’ll go ahead and archive it as well, so it should get visibility with the product team.