-
Enhancement
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
Consider a deployment with default microprofile-config.properties:
managementDefault=Default value from default microprofile-config.properties
Deployment is deployed on server with the following ConfigSource defined:
[standalone@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"}
}
}
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.
- is related to
-
-
- Verified
-
