avoid yaml confusion in postgres manifests

manifests/complete-postgres-manifest.yaml

@@ -1,6 +1,5 @@
 apiVersion: "acid.zalan.do/v1"
 kind: postgresql
-
 metadata:
   name: acid-test-cluster
 spec:
@@ -12,9 +11,9 @@ spec:
   teamId: "ACID"
   volume:
     size: 1Gi
-    #storageClass: my-sc
+#   storageClass: my-sc
   numberOfInstances: 2
-  users: #Application/Robot users
+  users: # Application/Robot users
     zalando:
     - superuser
     - createdb
@@ -24,8 +23,11 @@ spec:
   - 127.0.0.1/32
   databases:
     foo: zalando
-#Expert section
+
+# Expert section
+
   enableShmVolume: true
+# spiloFSGroup: 103
   postgresql:
     version: "10"
     parameters:
@@ -39,7 +41,6 @@ spec:
     limits:
       cpu: 300m
       memory: 300Mi
-  # spiloFSGroup: 103
   patroni:
     initdb:
       encoding: "UTF8"
@@ -48,42 +49,42 @@ spec:
     pg_hba:
     - hostssl all all 0.0.0.0/0 md5
     - host    all all 0.0.0.0/0 md5
-    #slots:
+#   slots:
-    #  permanent_physical_1:
+#     permanent_physical_1:
-    #    type: physical
+#       type: physical
-    #  permanent_logical_1:
+#     permanent_logical_1:
-    #    type: logical
+#      type: logical
-    #    database: foo
+#      database: foo
-    #    plugin: pgoutput
+#      plugin: pgoutput
     ttl: 30
     loop_wait: &loop_wait 10
     retry_timeout: 10
     maximum_lag_on_failover: 33554432
-  # restore a Postgres DB with point-in-time-recovery
+# restore a Postgres DB with point-in-time-recovery
-  # with a non-empty timestamp, clone from an S3 bucket using the latest backup before the timestamp
+# with a non-empty timestamp, clone from an S3 bucket using the latest backup before the timestamp
-  # with an empty/absent timestamp, clone from an existing alive cluster using pg_basebackup
+# with an empty/absent timestamp, clone from an existing alive cluster using pg_basebackup
-  # clone:
+#   clone:
-  #  uid: "efd12e58-5786-11e8-b5a7-06148230260c"
+#     uid: "efd12e58-5786-11e8-b5a7-06148230260c"
-  #  cluster: "acid-batman"
+#     cluster: "acid-batman"
-  #  timestamp: "2017-12-19T12:40:33+01:00" # timezone required (offset relative to UTC, see RFC 3339 section 5.6)
+#     timestamp: "2017-12-19T12:40:33+01:00" # timezone required (offset relative to UTC, see RFC 3339 section 5.6)
-  #  s3_wal_path: "s3://custom/path/to/bucket"
+#     s3_wal_path: "s3://custom/path/to/bucket"
 
-  # run periodic backups with k8s cron jobs
+# run periodic backups with k8s cron jobs
-  # enableLogicalBackup: true
+#   enableLogicalBackup: true
-  # logicalBackupSchedule: "30 00 * * *"
+#   logicalBackupSchedule: "30 00 * * *"
   maintenanceWindows:
   - 01:00-06:00 #UTC
   - Sat:00:00-04:00
-  #sidecars:
+# sidecars:
-  #  - name: "telegraf-sidecar"
+#   - name: "telegraf-sidecar"
-  #    image: "telegraf:latest"
+#     image: "telegraf:latest"
-  #    resources:
+#     resources:
-  #      limits:
+#       limits:
-  #        cpu: 500m
+#         cpu: 500m
-  #        memory: 500Mi
+#         memory: 500Mi
-  #      requests:
+#       requests:
-  #        cpu: 100m
+#         cpu: 100m
-  #        memory: 100Mi
+#         memory: 100Mi
-  #    env:
+#      env:
-  #      - name: "USEFUL_VAR"
+#        - name: "USEFUL_VAR"
-  #        value: "perhaps-true"
+#          value: "perhaps-true"

manifests/minimal-postgres-manifest.yaml

@@ -9,16 +9,11 @@ spec:
     size: 1Gi
   numberOfInstances: 2
   users:
-    # database owner
+    zalando: # database owner
-    zalando:
     - superuser
     - createdb
-
+    foo_user: [] # role for application foo
-    # role for application foo
-    foo_user: []
-
-  #databases: name->owner
   databases:
-    foo: zalando
+    foo: zalando # dbname: owner
   postgresql:
     version: "10"

manifests/standby-manifest.yaml

@@ -3,7 +3,7 @@ apiVersion: "acid.zalan.do/v1"
 kind: postgresql
 metadata:
   name: acid-standby-cluster
-  namespace: default 
+  namespace: default
 spec:
   teamId: "ACID"
   volume:
@@ -11,10 +11,10 @@ spec:
   numberOfInstances: 1
   postgresql:
     version: "10"
-  # Make this a standby cluster and provide the s3 bucket path of source cluster for continuous streaming.
+# Make this a standby cluster and provide the s3 bucket path of source cluster for continuous streaming.
   standby:
     s3_wal_path: "s3://path/to/bucket/containing/wal/of/source/cluster/"
 
   maintenanceWindows:
   - 01:00-06:00 #UTC
-  - Sat:00:00-04:00
+  - Sat:00:00-04:00