Support for reloading config #1619
Description
Affected Puppet, Ruby, OS and module versions/distributions
- Puppet: 8.9.0
- Distribution: Debian 11
- Module version: 5.0.0 (but the issue remains in master at the time of writing)
How to reproduce (e.g Puppet code you use)
Make a config change and wait for the refresh
What are you seeing
The service is always restarted and I cannot find any way of getting it to reload instead
What behaviour did you expect instead
That there is a way to make the service reload instead of restart at config changes
Any additional information you'd like to impart
Why is this important you might ask?
Well if you make a boo boo with the config (accidentally of course) then what happens is that NGiNX will not start because it will stop, read the config and realise it's invalid or otherwise faulty and refuse to start.
A reload on the other hand will examine the config, realise that it is b0rked and just not load it meaning that you still have a service with a working config up and running.