etcd3:
  hosts: IP1:2379,IP2:2379,IP3:2379,IP4:2379,IP5:2379,IP6:2379,IP7:2379,IP8:2379,IP9:2379
  protocol:
  username: username
  password: password

restapi:
  listen: "IP10:8008"
  connect_address: "IP11:8008"
  certfile: PATH-TO-CERT
  keyfile: PATH-TO-KEYFILE
  authentication:
        authentication:
        username: username
        password: password


bootstrap:
  # this section will be written into Etcd:/<namespace>/<scope>/config after initializing new cluster
  # and all other cluster members will use it as a `global configuration`
  dcs:
    ttl: 30
    loop_wait: 10
    retry_timeout: 10
    maximum_lag_on_failover: 1048576
    master_start_timeout: 30

    postgresql:
      use_pg_rewind: true
      remove_data_directory_on_rewind_failure: false
      remove_data_directory_on_diverged_timelines: false
      use_slots: false
      # The following parameters are given as command line options
      # overriding the settings in postgresql.conf.
      parameters:
        archive_command: PATH-TO-COMMAND
        max_connections: 1100
        wal_level: logical
        hot_standby: "on"
        max_wal_senders: 50
        max_replication_slots: 50
        max_worker_processes: 100
        wal_log_hints: "on"
        unix_socket_directories: '/var/run/postgresql/'
      recovery_conf:
        restore_command: PATH-TO-COMMAND
  # Some possibly desired options for 'initdb'
  initdb:  # Note: It needs to be a list (some options need values, others are switches)
    - encoding: UTF8
    - data-checksums
#  # Additional users to be created after initializing the cluster
  users:
    username: username
      password: password
      options:
        - replication
        - login

postgresql:
  # Custom clone method
  # The options --scope= and --datadir= are passed to the custom script by
  # patroni and passed on to pg_createcluster by pg_clonecluster_patroni
  create_replica_method:
    - pgbackrest
    - pg_clonecluster
  pgbackrest:
    command: PATH-TO-COMMAND
    keep_data: True
    no_params: True
  pg_clonecluster:
    command: PATH-TO-COMMAND

  listen: "IP10:5433"
  connect_address: "IP11:5433"
  use_unix_socket: true
  data_dir: /var/lib/postgresql/13/main
  bin_dir: /usr/lib/postgresql/13/bin
  config_dir: /etc/postgresql/13/main
  pgpass: /var/lib/postgresql/13-main.pgpass
  use_pg_rewind: true
  remove_data_directory_on_rewind_failure: false
  remove_data_directory_on_diverged_timelines: false
  use_slots: false
  parameters:
    archive_command: PATH-TO-COMMAND
    max_connections: 1100
    wal_level: logical
    hot_standby: "on"
    max_wal_senders: 50
    max_replication_slots: 50
    max_worker_processes: 100
    wal_log_hints: "on"
    unix_socket_directories: '/var/run/postgresql/'
  recovery_conf:
    restore_command: PATH-TO-COMMAND
  authentication:
    replication:
      username: username
      password: password
    rewind:
      username: username
      password: password
# A superuser role is required in order for Patroni to manage the local
# Postgres instance.  If the option `use_unix_socket' is set to `true', then
# specifying an empty password results in no md5 password for the superuser
# being set and sockets being used for authentication. The `password:' line is
# nevertheless required.  Note that pg_rewind will not work if no md5 password
# is set.
    superuser:
      username: username
      password: password
# uncomment the below and reload Patroni to set tags (will be commented again by Puppet!)
#tags:
  #nofailover: false
  #clonefrom: false

postgresql:
  parameters:
    archive_command: PATH-TO-COMMAND
    hot_standby: 'on'
    max_connections: 1100
    max_replication_slots: 50
    max_wal_senders: 50
    max_worker_processes: 100
    unix_socket_directories: /var/run/postgresql/
    wal_level: logical
    wal_log_hints: 'on'
  recovery_conf:
    restore_command: PATH-TO-COMMAND
  remove_data_directory_on_diverged_timelines: false
  remove_data_directory_on_rewind_failure: false
  use_pg_rewind: true
  use_slots: false
retry_timeout: 10
ttl: 30