update: source github.com/jsonnet-libs/k8s@d67f246c

1.20.6/_gen/postgresql/v1/backup.libsonnet

@@ -47,25 +47,25 @@
     apiVersion: 'postgresql.cnpg.io/v1',
     kind: 'Backup',
   } + self.metadata.withName(name=name),
-  '#spec':: d.obj(help='"Specification of the desired behavior of the backup. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status"'),
+  '#spec':: d.obj(help='"Specification of the desired behavior of the backup.\\nMore info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status"'),
   spec: {
     '#cluster':: d.obj(help='"The cluster to backup"'),
     cluster: {
       '#withName':: d.fn(help='"Name of the referent."', args=[d.arg(name='name', type=d.T.string)]),
       withName(name): { spec+: { cluster+: { name: name } } },
     },
-    '#onlineConfiguration':: d.obj(help="\"Configuration parameters to control the online/hot backup with volume snapshots Overrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza\""),
+    '#onlineConfiguration':: d.obj(help="\"Configuration parameters to control the online/hot backup with volume snapshots\\nOverrides the default settings specified in the cluster '.backup.volumeSnapshot.onlineConfiguration' stanza\""),
     onlineConfiguration: {
-      '#withImmediateCheckpoint':: d.fn(help='"Control whether the I/O workload for the backup initial checkpoint will be limited, according to the `checkpoint_completion_target` setting on the PostgreSQL server. If set to true, an immediate checkpoint will be used, meaning PostgreSQL will complete the checkpoint as soon as possible. `false` by default."', args=[d.arg(name='immediateCheckpoint', type=d.T.boolean)]),
+      '#withImmediateCheckpoint':: d.fn(help='"Control whether the I/O workload for the backup initial checkpoint will\\nbe limited, according to the `checkpoint_completion_target` setting on\\nthe PostgreSQL server. If set to true, an immediate checkpoint will be\\nused, meaning PostgreSQL will complete the checkpoint as soon as\\npossible. `false` by default."', args=[d.arg(name='immediateCheckpoint', type=d.T.boolean)]),
       withImmediateCheckpoint(immediateCheckpoint): { spec+: { onlineConfiguration+: { immediateCheckpoint: immediateCheckpoint } } },
-      '#withWaitForArchive':: d.fn(help='"If false, the function will return immediately after the backup is completed, without waiting for WAL to be archived. This behavior is only useful with backup software that independently monitors WAL archiving. Otherwise, WAL required to make the backup consistent might be missing and make the backup useless. By default, or when this parameter is true, pg_backup_stop will wait for WAL to be archived when archiving is enabled. On a standby, this means that it will wait only when archive_mode = always. If write activity on the primary is low, it may be useful to run pg_switch_wal on the primary in order to trigger an immediate segment switch."', args=[d.arg(name='waitForArchive', type=d.T.boolean)]),
+      '#withWaitForArchive':: d.fn(help='"If false, the function will return immediately after the backup is completed,\\nwithout waiting for WAL to be archived.\\nThis behavior is only useful with backup software that independently monitors WAL archiving.\\nOtherwise, WAL required to make the backup consistent might be missing and make the backup useless.\\nBy default, or when this parameter is true, pg_backup_stop will wait for WAL to be archived when archiving is\\nenabled.\\nOn a standby, this means that it will wait only when archive_mode = always.\\nIf write activity on the primary is low, it may be useful to run pg_switch_wal on the primary in order to trigger\\nan immediate segment switch."', args=[d.arg(name='waitForArchive', type=d.T.boolean)]),
       withWaitForArchive(waitForArchive): { spec+: { onlineConfiguration+: { waitForArchive: waitForArchive } } },
     },
-    '#withMethod':: d.fn(help='"The backup method to be used, possible options are `barmanObjectStore` and `volumeSnapshot`. Defaults to: `barmanObjectStore`."', args=[d.arg(name='method', type=d.T.string)]),
+    '#withMethod':: d.fn(help='"The backup method to be used, possible options are `barmanObjectStore`\\nand `volumeSnapshot`. Defaults to: `barmanObjectStore`."', args=[d.arg(name='method', type=d.T.string)]),
     withMethod(method): { spec+: { method: method } },
-    '#withOnline':: d.fn(help="\"Whether the default type of backup with volume snapshots is online/hot (`true`, default) or offline/cold (`false`) Overrides the default setting specified in the cluster field '.spec.backup.volumeSnapshot.online'\"", args=[d.arg(name='online', type=d.T.boolean)]),
+    '#withOnline':: d.fn(help="\"Whether the default type of backup with volume snapshots is\\nonline/hot (`true`, default) or offline/cold (`false`)\\nOverrides the default setting specified in the cluster field '.spec.backup.volumeSnapshot.online'\"", args=[d.arg(name='online', type=d.T.boolean)]),
     withOnline(online): { spec+: { online: online } },
-    '#withTarget':: d.fn(help='"The policy to decide which instance should perform this backup. If empty, it defaults to `cluster.spec.backup.target`. Available options are empty string, `primary` and `prefer-standby`. `primary` to have backups run always on primary instances, `prefer-standby` to have backups run preferably on the most updated standby, if available."', args=[d.arg(name='target', type=d.T.string)]),
+    '#withTarget':: d.fn(help='"The policy to decide which instance should perform this backup. If empty,\\nit defaults to `cluster.spec.backup.target`.\\nAvailable options are empty string, `primary` and `prefer-standby`.\\n`primary` to have backups run always on primary instances,\\n`prefer-standby` to have backups run preferably on the most updated\\nstandby, if available."', args=[d.arg(name='target', type=d.T.string)]),
     withTarget(target): { spec+: { target: target } },
   },
   '#mixin': 'ignore',