You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2017/05/16 20:47:04 UTC

[jira] [Updated] (DELTASPIKE-1212) Introduce a ConfigResolver.resolveAllProperties method

     [ https://issues.apache.org/jira/browse/DELTASPIKE-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Struberg updated DELTASPIKE-1212:
--------------------------------------
    Fix Version/s:     (was: 1.8.0)
                   1.8.1

> Introduce a ConfigResolver.resolveAllProperties method
> ------------------------------------------------------
>
>                 Key: DELTASPIKE-1212
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-1212
>             Project: DeltaSpike
>          Issue Type: New Feature
>          Components: Configuration
>    Affects Versions: 1.7.0
>            Reporter: John D. Ament
>             Fix For: 1.8.1
>
>
> Invoking ConfigResolver.getAllProperties does not expand out any inlined variables.  In addition, assume the following properties file and project stage = Development
> {code}
> some-service-url=${edge-server-url}/some-service
> edge-server-url=undefined
> edge-server-url.Development=http://development:8081
> edge-server-url.Staging=http://staging:8081
> edge-server-url.Production=http://prod:8081
> {code}
> calling {{getAllProperties}} returns the raw output of this file.  Introducing a new {{resolveAllProperties}} method would only return back the active values.  The expected result would be
> {code}
> some-service-url=http://development:8081/some-service
> edge-server-url=http://development:8081
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)