Include external configuration file as default to improve deployment and upgrade

I started to use Zabbix appliance (server, proxy and agent) by editing zabbix_*.conf. Almost every time I upgrade one of them, the classic

Configuration file '/etc/zabbix/zabbix_proxy.conf'

 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** zabbix_proxy.conf (Y/I/N/O/D/Z) [default=N] 

pops up.

So I reset the conf file to its default and add only one line at the end:

Include=/etc/zabbix/zabbix_proxy_local.conf

In this way, the diff are quicker to inspect, having moved all the customized parameters to an external file.

Still, I have to accept all new changes made by package distributor and then re-add the last line.

It would be convenient for sysadmin, if zabbix would include, as default, every .conf inside a directory, for example /etc/zabbix/zabbix_proxy.d/.conf. Like Apache or MySQL do. In this way using orchestration tool to upgrade many proxies and agent would proceed uninterruptedly.