Is your feature request related to a problem? Please describe.
Currently a deployment involves graceful restart of Apache httpd which reloads most configurations, however, there are certain changes e.g. MaxRequestWorker and ServerLimit which require non-graceful restart (stop and start to be on the safe side).
Describe the solution you'd like
Add another pipeline on Operational Task section to trigger Apache httpd restart.
Additional context
The reason why graceful restart is used by default is because if we do hard restart, it actually causes several seconds where Apache httpd will be down and this causes monitoring to detect downtime and triggers alerts subsequently. Hence AOC's stance is to perform graceful restart by default to avoid downtime detection. And by having Operational Task to perform hard restart, it indicates that the user explicitly decide to do the hard restart and taking the responsibility of managing the alerts that might be triggered.
Is your feature request related to a problem? Please describe. Currently a deployment involves graceful restart of Apache httpd which reloads most configurations, however, there are certain changes e.g. MaxRequestWorker and ServerLimit which require non-graceful restart (stop and start to be on the safe side).
Describe the solution you'd like Add another pipeline on Operational Task section to trigger Apache httpd restart.
Additional context The reason why graceful restart is used by default is because if we do hard restart, it actually causes several seconds where Apache httpd will be down and this causes monitoring to detect downtime and triggers alerts subsequently. Hence AOC's stance is to perform graceful restart by default to avoid downtime detection. And by having Operational Task to perform hard restart, it indicates that the user explicitly decide to do the hard restart and taking the responsibility of managing the alerts that might be triggered.