[jboss-jira] [JBoss JIRA] (WFLY-10852) smallrye-config: Consider logging a message when properties with same key and ordinal are present

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-10852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry moved WFWIP-60 to WFLY-10852:
----------------------------------------------

        Project: WildFly  (was: WildFly WIP)
            Key: WFLY-10852  (was: WFWIP-60)
    Component/s: MP Config
                     (was: MP Config)


> smallrye-config: Consider logging a message when properties with same key and ordinal are present
> -------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-10852
>                 URL: https://issues.jboss.org/browse/WFLY-10852
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: MP Config
>            Reporter: Michal Jurc
>            Assignee: Jeff Mesnil
>
> Consider a deployment with default {{microprofile-config.properties}}:
> {code}managementDefault=Default value from default microprofile-config.properties{code}
> Deployment is deployed on server with the following {{ConfigSource}} defined:
> {code}[standalone at localhost:9990 /] /subsystem=microprofile-config-smallrye/config-source=testdefault:read-resource
> {
>     "outcome" => "success",
>     "result" => {
>         "class" => undefined,
>         "dir" => undefined,
>         "ordinal" => 100,
>         "properties" => {"managementDefault" => "Value from WildFly microprofile-config-smallrye config-source"}
>     }
> }
> {code}
> Property {{"managementDefault"}} is always resolved to {{"Value from WildFly microprofile-config-smallrye config-source"}} in deployment.
> It would be useful to log a {{WARN}} level message when there is conflict like this with a notification of {{ConfigSources}} to save detective work in real world scenarios.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)