[
https://issues.apache.org/jira/browse/CAMEL-16412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-16412:
--------------------------------
Component/s: (was: camel-properties)
camel-core
> Environment Variables in Location no longer working
> ---------------------------------------------------
>
> Key: CAMEL-16412
> URL: https://issues.apache.org/jira/browse/CAMEL-16412
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 3.7.3, 3.8.0
> Reporter: Remco Schoen
> Priority: Minor
> Fix For: 3.7.4, 3.10.0
>
>
> We are using environment variables in our Location of the
> propertiesPlaceholder to control the location of our properties during the
> different stages of our deployments, according to his doc:
> [https://camel.apache.org/manual/latest/using-propertyplaceholder.html#UsingPropertyPlaceholder-UsingSystemandEnvironmentVariablesinLocations.]
> <propertiesLocation resolver="file"
> path="${env.SECRETS_LOCATION}/tif.secrets"/>
> This now results in a FileNotFoundException:
>
> {code:java}
> Caused by: java.io.FileNotFoundException: ${env:SECRETS_LOCATION}/tif.secrets
> (No such file or directory)Caused by: java.io.FileNotFoundException:
> ${env:SECRETS_LOCATION}/tif.secrets (No such file or directory) at
> java.base/java.io.FileInputStream.open0(Native Method) at
> java.base/java.io.FileInputStream.open(FileInputStream.java:219) at
> java.base/java.io.FileInputStream.<init>(FileInputStream.java:157) at
> java.base/java.io.FileInputStream.<init>(FileInputStream.java:112) at
> org.apache.camel.component.properties.FilePropertiesSource.loadPropertiesFromLocation(FilePropertiesSource.java:51)
> ... 63 more{code}
>
> I think the change in CAMEL-15781 causes this.
>
> A workaround is to replace "env:" with "env.".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
