Previously this was handled by repmgrd but if a standby is promoted directly this will leave the metadata in an incorrect state.
When using the default pg_basebackup method to clone a standby together with the `--ignore-external-config-files` option, there's no need to test for a working SSH connection - which may not be desirable in many use-cases anyway. Per issue #64 in GitHub.
In some circumstances (primarily when executing `repmgr standby clone`) the `repmgr.conf` file is not mandated. However this means the repmgr schema is not known, and any attempt to create an event record will result in a log warning, which may cause confusion as to the success of the operation. It might be better to mandate providing `repmgr.conf` in all circumstances. Per report in #53 .