3 ms·
Although it doesn't directly go against what you're saying, many Unix daemons have supported HUP signals for decades which can achieve the same outcome. No need
by 22c 3y ago
Although it doesn't directly go against what you're saying, many Unix daemons have supported HUP signals for decades which can achieve the same outcome. No need to configure via API, just change the configuration on disk and send HUP.
I suppose arguably that becomes a bit trickier for containers, so perhaps that's why you'd want to configure via an API?
- hamandcheese 3y agoTo me this is identical - mutable state is mutable state, whether it starts on disk first makes no difference.
- 22c 3y agoThere is a slight difference to me as having another service run (the API) is an additional attack vector to worry about from a security perspective. I would also say it's easier to enforce good "IaC hygiene" when the configs are managed via configuration files. They can go through a code review process, deployed via existing config management systems etc.
- pstuart 3y agoNginx can reload configs on HUPs -- https://docs.nginx.com/nginx/admin-guide/basic-functionality/runtime-control/ https://docs.nginx.com/nginx/admin-guide/basic-functionality...