e933908084
Previously, the operator put pg_hba into the bootstrap/pg_hba key of Patroni. That had 2 adverse effects: - pg_hba.conf was shadowed by Spilo default section in the local postgresql configuration - when updating pg_hba in the cluster manifest, the updated lines were not propagated to DCS, since the key was defined in the boostrap section of Patroni. Include some minor refactoring, moving methods to unexported when possible and commenting out usage of md5, so that gosec won't complain. Per https://github.com/zalando-incubator/postgres-operator/issues/330 Review by @zerg-junior |
||
|---|---|---|
| .. | ||
| cluster.go | ||
| cluster_test.go | ||
| exec.go | ||
| filesystems.go | ||
| k8sres.go | ||
| k8sres_test.go | ||
| pg.go | ||
| pod.go | ||
| resources.go | ||
| sync.go | ||
| types.go | ||
| util.go | ||
| volumes.go | ||