As discussed on the Dec 18th TAC call (see notes here), Iniz 2.1.0 will eventually be released with the new Iniz Validator embedded. And, before the 2.1.0 release, this new tool can be tested through the latest snapshot of Iniz.
I am kindly requesting for you to do so as your feedback will be invaluable ahead of the 2.1.0 release.
For the devs out there and for the record here is the PR:
- [#84] Added Initializer Validator. by mks-d · Pull Request #88 · mekomsolutions/openmrs-module-initializer · GitHub
(Special thanks to @ibacher who actually did review it, kudos!)
In a nutshell the Initializer Validator is a standalone fatjar to make dry runs of your OpenMRS configs and to report on any errors. This enables developers and implementers to be warned well ahead of time that a config would fail when loaded on real OpenMRS instances.
Btw I strongly invite you to read:
I envision two main use cases:
For business analysis profiles to use it on their local machines and ensure that all is well with the OpenMRS configs that they are putting together.
To fail invalid OpenMRS configs builds. That would be mainly useful for CI processes, but also for developers of course, ahead of pushing.
At Mekom and PIH there is certainly a lot of interest to start modifying the current OpenMRS configs CI builds so that they trigger the validation. And as suggested by @mseaton during the Dec 18th’s TAC call, this could be done via PIH’ openmrs-packager-maven-plugin to make this an easy change in existing POMs. That’s probably the very next thing on our roadmap.
Finally, please note that a couple of other changes have been introduced as well, most notably:
- Much much better and prettier logging.
- The ability to control Iniz’ behaviour more finely through a handful of new runtime properties.