Running pgwatch on etcd https endpoints

[MarBro11]

Try to run patroni monitoring via pgwatch 6.0.0 without success. As I can see in source code, default endpoint that is build in resolver.go, func NewHostConfig(URI string) (hc HostConfig, err error) http:// endpoint is created by default. Is possible pgwatch can gatcher data from https etcd endpoint?

[yudin-s]

With the current resolver, an HTTPS etcd endpoint is not expressible through conn_str. NewHostConfig() accepts the logical etcd:// scheme and then constructs every etcd endpoint as http:// + host; it rejects https as an unsupported DCS type. The URI parser has no endpoint-scheme option.

The TLS query fields (ca_file, cert_file, key_file) are read and passed into the etcd client, and the current Patroni guide documents them, but they do not change that hard-coded endpoint construction. So a configuration such as etcd://etcd1:2379/...?... can provide client/CA material, yet it cannot explicitly select an https://etcd1:2379 endpoint.

For a TLS-only etcd listener, I would treat this as a pgwatch resolver limitation/bug rather than try to encode https:// inside the host list. The safe workaround is an HTTP endpoint only if it is intentionally protected by a local/private proxy; otherwise it needs a small resolver change that preserves an endpoint scheme (or adds an explicit etcd_scheme=https option), plus a test covering the generated endpoint. Do not work around it by disabling certificate verification.

Relevant current sources: NewHostConfig and the Patroni TLS-material example.

If this explains the behavior, please mark the answer as answered.