Patroni is always restarted when configuration file changes even though reload is enough #89
Description
Currently, the module always restarts the Patroni service whenever the configuration file changes.
This behavior is overly aggressive: many PostgreSQL parameters under postgresql.parameters (e.g. log_rotation_size, work_mem, etc.) do not require a full service restart. A simple patronictl reload is sufficient for these parameters to take effect.
The module should only restart the patroni service when absolutely required and just run patronictl reload otherwise.
This change would greatly reduce unnecessary downtime and improve operational safety when managing Patroni via Puppet.