As a sysadmin I want to use MicroProfile Config API to configure my installation #7000
Description
Now that Payara 5 is actually happening with the release of Dataverse 5 (thank you so much folks!!!), we should re-raise the topic (formerly #5187) of starting to use some of the goodies coming along with this.
As a system admin pushing to cloud, I would greatly benefit from having the possibility to get configuration inside my instance not via mangling with JVM options and database settings. Instead, I would like to see this being more flexible and combined with a hierarchy.
This will also benefit greatly any classic installation, as configuration will be easier than dealing with domain.xml and friends.
Introduce MicroProfile Config API and its support in Payara 5 for code variables and configuration variables, combining 1 & 2.
This will open up the following work items:
- Replace all the
System.getProperty(). - Look for the database settings and how to replace them
- Make all of this backward compatible
- Do solid configuration validation
- Look into replacing installers/container scripts configuration of JDBC, JMS, etc with annotations, which are then configured via Config API
Things going on:
- Update to Payara 5.2021.3 #7700 updating to Payara 5.2021.4 to enable MPCONFIG 2.0 support
- MPCONFIG: identify non-static settings #7639
- Introduce using MicroProfile Config API #7457
- Move Java Mail configuration to application #7424
- Move database configuration into application #7418
- As a developer, I want changes I make to the front end to be visible when I deploy from Netbeans #6953 / 6953 mpconfig context param #7695