vy commented on issue #2852: URL: https://github.com/apache/logging-log4j2/issues/2852#issuecomment-2311769547
> Allows developers/devops to deploy Kubernetes config maps (one file per-subdirectory) without using a special type of volume (aka projected volume). @mattrpav, thanks for clarifying that you were referring to OS containers – [as I indicated earlier](https://github.com/apache/logging-log4j2/issues/2852#issuecomment-2309908776), @ppkarwasz thought you were referring to Servlet containers. I am still keen on supporting configuration directories you proposed, but to better understand what is falling short in the current knobs: You can attach your Log4j configuration files in whichever way you want (bundle them in JARs, mount them using ConfigMaps, regular/projected volumes, etc.) and use the `LOG4J_CONFIGURATION_FILE` environment variable to point to the effective one at runtime. Why is this not a viable option for you? -- 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]
