Configuration as Code PI System wide

"As a business owner, I want to set up change control procedures where any change to the PI System, be it the data archive, asset framework, PI Interfaces, PI Connectors, or any other component is done through a change in source controlled configuration files so I can track change requests, assign them to reviewers, and automatically apply them to production after the changes are applied to a test environment and satisfy automated tests. The configuration should be flexible enough to work with other deployment scripts so new servers can be automatically provisioned and configured if the configuration requires it." Essentially I'd like to be able to apply modern configuration as code and continuous deployment strategies to all components of the PI System. Parts of this are already possible with the Desired State Configuration libraries (covering PI DA and AF), but a lot of components cannot be configured through code and require an administrator to use a user interface to interact with the software, and automated tests cannot be run against most components easily. These principles are used in management of many business critical real-time applications in the IT space. Being able to do this with the PI System will enable enforced change control procedures and reduce breaking changes to production environments in large organisations.