Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
configadmin-interpolation-plugin-1.2.6
-
None
Description
I have the following construct:
$[env:MQTT_WRITE_HOST;default='$[prop:MQTT_WRITE_HOST;default=some.host]']
The Goal is, env -> prop -> default
The result unfortunately is not as expected. if I have no default for the props statement, the fallback works and it tries to resolve the property if the env is not set. If I have the second default for the case that nothing is set, the env immediately defaults to "some.host]".
The Quotes for the default make no difference in this case, even if I only quote the value of the last default. My current workaround is $[env:MQTT_WRITE_HOST;default=]$[prop:MQTT_WRITE_HOST;default=some.host]
Additionally a convinient version like propEnv and envProp would be nice to cover suche a case in on statement.