As per https://help.sonatype.com/repomanager3/new-database-options/configuring-nexus-repository-pro-for-h2-or-postgresql#ConfiguringNexusRepositoryProforH2orPostgreSQL-ExtraConfigurationOptionsforPostgreSQL
Currently there are several properties files to create and the add properties into in order to use Postgres as the database implementation
- Create the <data-dir>/etc/nexus.properties file and add the following line:
- Create the <data-dir>/etc/fabric directory.
- In this directory, create nexus-store.properties; below is a sample that you will need to update with the appropriate configuration.
If using AWS Aurora as your database, you will need to include gssEncMode=disable as a query parameter of the JDBC URL.
You can now start your Nexus Repository instance and use a PostgreSQL database.
The more files to create, the more potential confusion about what is actually consumed and more risk of misconfiguration. The support team and the customer will need to look in more places for problems. There is already a well established pattern for configuring runtime properties, via nexus.properties file and system properties, even set via bin/nexus.vmoptions.
Do not require creating new property files in order to use datastore related properties. Instead namespace the datastore specific properties and allow those properties be consumed as typical properties are, via etc/nexus.properties, as system properties, etc. Re-use the algorithm that already exists that merges all properties from the various places NXRM already consumes them.