Merge pull request #6065 from EnterpriseDB/docs/tpa/add-missing-rel-note

Add missing release note for TPA 23.34

Author: djw-m

product_docs/docs/tpa/23/rel_notes/tpa_23.34_rel_notes.mdx

@@ -16,6 +16,7 @@ New features, enhancements, bug fixes, and other changes in Trusted Postgres Arc
 | Enhancement | TPA now runs the EFM `upgrade-conf` command on new cluster deployments to benefit from the comments and inline documentation that are added to both `<cluster_name>.properties` and `<cluster_name>.nodes` files.  |
 | Enhancement | TPA can now set up EFM clusters using hostname resolution instead of IP addresses for `bind.address` value.  This can be invoked with tha `--efm-bind-by-hostname` option for the configure command or `efm_bind_by_hostname: true|false` in cluster_vars  section of config.yml. |
 | Enhancement | TPA now supports setting the EFM properties that added in EFM 4.9:  `enable.stop.cluster: boolean, default true`, `priority.standbys: default ''`, `detach.on.agent.failure: boolean, default false`, `pid.dir: default ''`.  |
+| Enhancement | TPA can now configure pgBouncer to use `cert` authentication for connections from pgBouncer to Postgres. This is enabled by setting `pgbouncer_use_cert_authentication` to true in cluster_vars. When enabled, the authentication method for users connecting to pgBouncer is also changed from `md5` to `scram-sha-256`. |
 | Change | TPA no longer supports RAID creation on AWS. |
 | Change | Removed EFM dependency for resolving upstream_primary. Previously, EFM was queried for the current primary on a deploy after a switchover. If EFM is not running, this will fail. Now the cluster_facts collected through Postgres are used to determine the current primary after a switchover, removing the dependency on EFM.  |
 | Change | In EFM clusters, the `upstream_primary` is now correctly updated after switchover,  resulting in the correct `auto.reconfigure` setting be set on replicas. Standbys now follow the new primary.   |