Show user in password prompt (fixing regression)

[rolandwalker]

Description

It would seem that there was a regression in #1436, and we need to redo #1291.

In order to do this, we have to lose some special DSN logic. There is just no way under the current setup, since for instance the SSL params get parsed out of the DSN before calling connect().

Once solution could be to do all configuration parsing early, a long-term goal.

Here we replace the DSN fallthrough with a warning message.

The password_from_file logic is incidentally improved.

Checklist

• I've added this contribution to the changelog.md.
• I've added my name to the AUTHORS file (or it's already there).
• I ran uv run ruff check && uv run ruff format && uv run mypy --install-types . to lint and format the code.

[scottnemes]

I removed it on purpose because when prompting the user for a password at the start, the username is not yet known unless the --user/-u option is passed. So you'd have to move the config checks up higher, or it just shows None. But if that's what you want, then works as-is then anyway.

uv run mycli --password
Enter password for None:

uv run mycli -u scottn --password
Enter password for scottn:

mycli/mycli/main.py

Line 507 in a237ee9

user = user or cnf["user"] or os.getenv("USER")

[rolandwalker]

I see. We don't have cnf yet.

[scottnemes]

Why are you removing the logic to catch the case where they use the password flag and also provide a DSN? We keep going around in circles on this, but seems you just want it this way and did not previously say so.

[scottnemes]

Never mind I realized you mentioned this in your original PR description. You're removing it because it changes the way things work when all of the related logic is moved to the new location. I'll see if I can figure anything else out. Though I'd question if having the user in the prompt is more important, but that part is up to you.

[scottnemes]

I pushed a commit that I believe gives you what you wanted plus keeping the original functionality (was easier than trying to explain it, so feel free to revert if you don't want it).

[scottnemes]

Made one more small change; realized that when I moved the line up to check the vendor configs for a password it changed the password hierarchy, so I moved it back to where it was now that it worked as expected.