PGPASSFILE ignored when use --ssh-tunnel

[DiegoDAF]

Hi again, team!

I ❤️ pgcli due to this parameter --ssh-tunnel, I think it is the real GOAT.

The thing is, I do not understand how to use the PG* env variables at the same time I try to connect via tunnel.

For example, pgAdmin4 uses my local .pgpass file even when I use SSH tunnels (they use the same library, as far as I know), but I'm not a developer to understand the difference.

In my example, I checked the connection via a bastion server called lm2.

Could someone help me use the pgpass via SSH tunnels?

Thanks a lot.
Diego.

[diego-feito-stori]

The problem was in the "concept" of a tunnel.
In my pgpass, I have the fqdn, but from my local, I need to use 127.0.0.1 instead.
Even with a rule for tunneling in the config, the problem remains the same.
Now I have two questions:

1. Can I use the FQDN instead of the local entry when I use a tunnel? (like in pgadmin)
2. If the cert has a password, it is not possible to save it or ask.

[DiegoDAF]

I made this bash script as a workaround,

require:

• DSN entries configured correctly in [alias_dsn] entry in the config file /home/daf/.config/pgcli/config as shown in the image:

• the bastions configured in [ssh tunnels] in the same config file /home/daf/.config/pgcli/config as shown in the image:

The script: pgcli-interactive.sh

Some screenshots:

Ofc, its a POC, but it works until I can create a PR to the main project ;P