I believe to comply with modern infrastructures, it would be helpful if Zabbix server would support a kind of configuration provisioning. By that I mean a way to supply configurations to Zabbix that are to be applied at the moment the server awakes the first time and gets its connection to the database.

Of course, it is possible to interact with the already running server and change configurations via API, but the requires authentication, needs a check whether the instance was just newly deployed or is being there already for a while, ....

Think about following exemplary scenario: you want to deploy Zabbix Server instances for your clients, one for each of them. You have a unified set of templates that you want to offer them, maybe a SAML configuration that can be done in an automated way, probably you also want some users, groups, roles, and hosts monitored to be generated for each of those new instances. With configuration provisioning (probably some yaml files in a specific directory, which could then be placed there by any Ansible or whatever orchestration tool) there would be a very flexible way to do that. Also in traditional environments that can make a lot of sense.

This feature request is btw inspired by Grafana which has a functionality like that.