MIME-Version: 1.0
From: Andrew Coleman <penguincoder@gmail.com>
Date: Thu, 27 Jun 2019 08:27:27 -0400
Message-ID: 
 <CANNh3aX1ZdOrXZx_92=8QJc0ZzBYYghCaAjRLkOJ69=UGrftvA@mail.gmail.com>
Subject: passwords enabled by default
To: pgadmin-hackers <pgadmin-hackers@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000009ae58e058c4d49cf"
Precedence: bulk

--0000000000009ae58e058c4d49cf
Content-Type: text/plain; charset="UTF-8"

Recently, while testing my changes to entrypoint.sh in Docker, I noticed
that you cannot import or export passwords via the servers.json file. You
can get around this by setting the PassFile option in servers.json, but
that still doesn't work correctly. For me to make this work, I had to also
set the `PGPASSFILE` to the full path location of the pgpass file generated
for me by Helm.

To clarify, I know how many servers I want to connect to and how to find
their passwords in Kubernetes via their secret, and I use Helm to stitch
all of that together into a pgpass file that psql and pgadmin4 can use to
connect to the servers without user intervention.

The presence of the pgpass file and the reference to that file in the
servers.json was not enough to allow pgadmin4 to connect to the servers, I
also had to set `PGPASSFILE` in my Helm chart to make this work.

This seems like another good ticket, no? I know where to add them and I'll
put a patch in place, but I could sure use a little bit of guidance on the
copy portion of the documentation. I know why it works for me, but would
anyone conceivably use this in a non-Dockerized deployment?

Thanks,
Andrew

--0000000000009ae58e058c4d49cf
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Recently, while testing my changes to entrypoint.sh i=
n Docker, I noticed that you cannot import or export passwords via the serv=
ers.json file. You can get around this by setting the PassFile option in se=
rvers.json, but that still doesn&#39;t work correctly. For me to make this =
work, I had to also set the `PGPASSFILE` to the full path location of the p=
gpass file generated for me by Helm.</div><div><br></div><div>To clarify, I=
 know how many servers I want to connect to and how to find their passwords=
 in Kubernetes via their secret, and I use Helm to stitch all of that toget=
her into a pgpass file that psql and pgadmin4 can use to connect to the ser=
vers without user intervention.</div><div><br></div><div>The presence of th=
e pgpass file and the reference to that file in the servers.json was not en=
ough to allow pgadmin4 to connect to the servers, I also had to set `PGPASS=
FILE` in my Helm chart to make this work.</div><div><br></div><div>This see=
ms like another good ticket, no? I know where to add them and I&#39;ll put =
a patch in place, but I could sure use a little bit of guidance on the copy=
 portion of the documentation. I know why it works for me, but would anyone=
 conceivably use this in a non-Dockerized deployment?</div><div><br></div><=
div>Thanks,</div><div>Andrew<br></div></div>

--0000000000009ae58e058c4d49cf--