From 1ff06677a5bba54c495775511c729b87e5d18e4e Mon Sep 17 00:00:00 2001
From: Jehan-Guillaume de Rorthais <jgdr@dalibo.com>
Date: Tue, 29 Sep 2020 14:18:07 +0200
Subject: [PATCH] Use OCF_RESKEY_CRM_meta_notify to check notify meta parameter

Per discussion and suggestion from clusterlabs users mailing list. See
https://lists.clusterlabs.org/pipermail/users/2019-April/025720.html
---
 script/pgsqlms | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/script/pgsqlms b/script/pgsqlms
index 7dd695e..ada9a21 100755
--- a/script/pgsqlms
+++ b/script/pgsqlms
@@ -1303,10 +1303,8 @@ sub pgsql_validate_all {
     }
 
     # check notify=true
-    $ans = qx{ $CRM_RESOURCE --resource "$OCF_RESOURCE_INSTANCE" \\
-                 --meta --get-parameter notify 2>/dev/null };
-    chomp $ans;
-    unless ( lc($ans) =~ /^true$|^on$|^yes$|^y$|^1$/ ) {
+    unless ( defined $ENV{'OCF_RESKEY_CRM_meta_notify'}
+        and lc($ENV{'OCF_RESKEY_CRM_meta_notify'}) =~ /^true$|^on$|^yes$|^y$|^1$/ ) {
         ocf_exit_reason(
             'You must set meta parameter notify=true for your master resource'
         );