#8852 - ldap sync output filter

edit.sh

Index: edit.sh
diff --git a/edit.sh b/edit.sh
new file mode 100755
index 0000000000000000000000000000000000000000..f4c25474c4533751cf4ddb9c79e3ea6f9d755e94
--- /dev/null
+++ b/edit.sh
@@ -0,0 +1,28 @@
+#!/bin/sh
+
+# Filtering out uninformative output lines from the ldap-sync cron job script

[f.lopez, 2018/05/29 21:18:48]

I don't think this script is only for cron jobs, even tho this could be the use
case right now, also don't use gerund or infinitive for the description,
"Filtering" -> "Filter"

+
+last_updated=""
+
+while read line; do
+

[f.lopez, 2018/05/29 21:18:49]

be consistent here, either always use a blank line between each block, or not,
but if you are using blank lines, then it should be one between `esac` and
`done`, in this case tho, for readability, I wouldn't use blank lines

+  case $line in
+

[f.lopez, 2018/05/29 21:18:48]

not blank lines here either

+    *Updating*|*Creating*)
+      last_updated="$line"
+      ;;
+

[f.lopez, 2018/05/29 21:18:48]

not blank lines between each option either

+    *-\>*)
+      echo $last_updated

[f.lopez, 2018/05/29 21:18:48]

this is a regression, I mentioned in the first code review that, as a general
rule, and unless you know what you are doing, you should always quote variables
to avoid globbing and word splitting.

Please go through the following link
http://www.tldp.org/LDP/abs/html/quoting.html

+      echo $line
+      ;;
+
+    *Found*|*\#*|*Synchronizing*)

[f.lopez, 2018/05/29 21:18:48]

We always avoid modifying unrelated changes, in this case, if you need to
modify/add/delete a term that don't need special treatment, you will modify the
whole line, which would be an unrelated changes,

something like:

```
*Found* | \
*\#* | \
*Synchronizing*)
```

+      continue
+      ;;
+
+    *)
+      echo $line
+      ;;
+  esac
+done