|
| 1 | +###################################################################### |
| 2 | +# ATTENTION! Managed by SaltStack. # |
| 3 | +# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN! # |
| 4 | +###################################################################### |
| 5 | +# |
| 6 | +# PostgreSQL User Name Maps |
| 7 | +# ========================= |
| 8 | +# |
| 9 | +# Refer to the PostgreSQL documentation, chapter "Client |
| 10 | +# Authentication" for a complete description. A short synopsis |
| 11 | +# follows. |
| 12 | +# |
| 13 | +# This file controls PostgreSQL user name mapping. It maps external |
| 14 | +# user names to their corresponding PostgreSQL user names. Records |
| 15 | +# are of the form: |
| 16 | +# |
| 17 | +# MAPNAME SYSTEM-USERNAME PG-USERNAME |
| 18 | +# |
| 19 | +# (The uppercase quantities must be replaced by actual values.) |
| 20 | +# |
| 21 | +# MAPNAME is the (otherwise freely chosen) map name that was used in |
| 22 | +# pg_hba.conf. SYSTEM-USERNAME is the detected user name of the |
| 23 | +# client. PG-USERNAME is the requested PostgreSQL user name. The |
| 24 | +# existence of a record specifies that SYSTEM-USERNAME may connect as |
| 25 | +# PG-USERNAME. |
| 26 | +# |
| 27 | +# If SYSTEM-USERNAME starts with a slash (/), it will be treated as a |
| 28 | +# regular expression. Optionally this can contain a capture (a |
| 29 | +# parenthesized subexpression). The substring matching the capture |
| 30 | +# will be substituted for \1 (backslash-one) if present in |
| 31 | +# PG-USERNAME. |
| 32 | +# |
| 33 | +# Multiple maps may be specified in this file and used by pg_hba.conf. |
| 34 | +# |
| 35 | +# No map names are defined in the default configuration. If all |
| 36 | +# system user names and PostgreSQL user names are the same, you don't |
| 37 | +# need anything in this file. |
| 38 | +# |
| 39 | +# This file is read on server startup and when the postmaster receives |
| 40 | +# a SIGHUP signal. If you edit the file on a running system, you have |
| 41 | +# to SIGHUP the postmaster for the changes to take effect. You can |
| 42 | +# use "pg_ctl reload" to do that. |
| 43 | + |
| 44 | +# Put your actual configuration here |
| 45 | +# ---------------------------------- |
| 46 | + |
| 47 | +# MAPNAME SYSTEM-USERNAME PG-USERNAME |
| 48 | + |
| 49 | +{%- for mapping in mappings %} |
| 50 | +{{ '{0:<15} {1:<22} {2}'.format(acl) -}} |
| 51 | +{% endfor %} |
0 commit comments