carterkozak opened a new pull request #732:
URL: https://github.com/apache/logging-log4j2/pull/732
Previously lookups between configuration properties weren't evaluated
until they were used in the configuration, which resulted in
behavior more prohibitive for RoutingAppenders than anticipated.
This attempts to provide a safer, more compatible lookup strategy
with consistent behavior between users.
The risk is that changes in edge-case behavior impact the entire
configuraiton surface, not only the more obscure runtime consumers.
For example, a property defined thusly (note the escaped lookup)
`<property name="foo">Date is $${date:YYYY-MM-dd}</property>`
When used would result in `Date is ${date:YYYY-MM-dd}`
rather than `Date is 2022-01-27`, becuase initially when
the configuration is parsed, lookups aren't evaluated on properties,
which previously stripped one level of escapement.
The new behavior is easier to understand, but may result in some
friction for consumers.
**TODO(ckozak): needs additional test coverage, but I'd like to share the
concept first**
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
