Using API configuration.export and configuration.import so that I can change control all of my template changes and automate pushing them to multiple zabbix instances to keep them all in-sync.  On my alpha and beta instances this works great as there are very few hosts defined.

I'm now implementing my production instance that has ~700 linux hosts defined and will probably have twice that in a few days.  With a php memory limit of 8g the import fails because it runs out of memory.  Bump the memory limit to 16g and rerun and the process fails at about the same place because it runs out of time.

I could still bump the memory and timeouts a little higher, but the reality is that I'm about to double the number of hosts using this template and I will just be right back to this same problem.

This cannot be the intended design/behavior of this API call.  Doing the import through the front-end GUI works fine, but it also doesn't use the API and instead does direct DB access.

This design flaw / bug pretty much makes it impossible to automate template imports.  Please let me know if you need additional information.