mattrpav commented on issue #2852:
URL:
https://github.com/apache/logging-log4j2/issues/2852#issuecomment-2310245572
> > Build a Java-based container ...
>
> @mattrpav, are you referring to OS containers (Docker, Podman, etc.) or
Java servlet containers? (I have the impression that you're referring to the
former, while @ppkarwasz is talking about the latter. Hence, I feel like we are
not on the same page.)
What specifically does not seem to align to you?
> I had two other alternatives in mind:
>
> 1. **Support wildcards:** e.g.,
`-Dlog4j2.configurationFile=/opt/app/conf/log.d/*` – This matches the way `-cp`
JVM option works and the [JEP 458: Launch Multi-File Source-Code
Programs](https://openjdk.org/jeps/458) features freshly delivered in Java 22.
A reasonable set of default filename globs should suffice-- log4j2*.json,
log4j2*.yaml, log4j2*.xml, log4j2*.properties, etc.
> 2. **Support glob patterns:** e.g.,
`log4j2.configurationFile=/opt/app/conf/log.d/**/*` – This would be pretty
powerful, but requires an in-house glob implementation, which sort of renders
this option an overkill.
If the default behavior is defined to scan sub-directories, this should not
be needed.
Defaults:
1. Follow symlinks
2. Scan sub-directories
3. Limit sub-directory depth to a reasonably high value (ie. 16 or 32). This
will provide flexibility, be performant, and provide an escape hatch for
problematic scenarios (symlink loops, etc)
--
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]
