Well, at least I found a solution:
I took the usual application context for cloud configuration. In this context, I placed the sharedCommonServers.properties file in the default application properties file with a special profile.
Rename:
'sharedCommonServers.properties' to 'application-commonServers.properties'
Extending profile settings with the 'commonServers' spring, the cloud configuration further extracts it.
Make sure that there are no overlapping property keys in the other profile line.
So, in my environment, when I installed ...
-Dspring.profiles.active=prod,commonServers'
... I get my default prod configuration and those marked as commonServers profiles.
application.properties application-prod.properties application-commonServers.properties // the additional one <appname>.properties <appname>-prod.properties // and <appname>-commonServers.properties if I would need it
Thanks for your suggestions and thoughts!
source share