I’m new to the BloomReach platform and I’m wondering if some kind individual might be able to provide me with direction on best practices for setting environment-specific properties that can then be accessed by, say, Spring beans.
This is something that can come up if we need to integrate with a third-party service provider to specify some sort of property (eg. “client.id”) whose value might differ between the DEV and STAGING environments, for example.
To illustrate more clearly, in a shared development server (eg. “DEV”), I might need to specify:
And similarly in a STAGING/QA environment, I might need to use the same property name, but with a different value like so:
Is there a standard approach to setting such environment-specific properties in BloomReach?
One approach that came to my mind was to try to add a new String property to the “/hst:hst/hst:hosts/dev-localhost” virtual host group in the CMS Console, and then define other virtual host groups for other environments (QA, UAT, PROD, whatever). However, I quickly discovered that I cannot just add any arbitrary string property to an hst:virtualhostgroup.
Any help in the matter would be very gratefully appreciated!