We have another report from the community that it is not clear which database the drop command is actually accessing, it is in this thread here: https://dlthub-community.slack.com/archives/C04DQA7JJN6/p1714050325808869. From my perspective the bottom line should be, that all cli commands that modify the destination in some way should print a message stating that that the credentials are not taken from the code (but rather toml file) and then also print the connection string and dataset to this destination, without the credentials, for the user to review.
rudolfix
commented
3 months ago
The current drop command requires additional credentials setting. We want to make it more user friendly: https://dlthub-community.slack.com/archives/C04DQA7JJN6/p1712059067366979
We have another report from the community that it is not clear which database the drop command is actually accessing, it is in this thread here: https://dlthub-community.slack.com/archives/C04DQA7JJN6/p1714050325808869. From my perspective the bottom line should be, that all cli commands that modify the destination in some way should print a message stating that that the credentials are not taken from the code (but rather toml file) and then also print the connection string and dataset to this destination, without the credentials, for the user to review.