mogranovitch
3 years agoOccasional Contributor
Use of global/project property on setting Database Configuration
Hi guys,
I'd like to stop using hard coded values for setting Password on each Database configuration: I have multiple databases for multiple projects/environments and passwords changing every month.
When I tried to use global/project property to store passwords - to have all of them at one place - I do not see that password property parameter I'm trying to set during configuration is being read.
Here is example for storing it as Project property:
password | context.expand( '${#Project#dataUserPass}' )
Is there a way to use a parameter in this situation?
Thank you!