From 5e1d86e31e9bf04d7069c075b10068858c292fdb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Manuel=20G=C3=B3mez?= Date: Mon, 16 Apr 2018 18:23:41 +0200 Subject: [PATCH] Fix clone timestamp key in example manifest (#276) It was set to `endTimestamp`, but it should be `timestamp`. --- manifests/complete-postgres-manifest.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manifests/complete-postgres-manifest.yaml b/manifests/complete-postgres-manifest.yaml index 68bda81cf..2f929bc2c 100644 --- a/manifests/complete-postgres-manifest.yaml +++ b/manifests/complete-postgres-manifest.yaml @@ -49,7 +49,7 @@ spec: # with an empty/absent timestamp, clone from an existing alive cluster using pg_basebackup # clone: # cluster: "acid-batman" - # endTimestamp: "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) maintenanceWindows: - 01:00-06:00 #UTC - Sat:00:00-04:00