The Kubernetes and Docker plugins are for additional lookup variables, though based on how I’ve used Kubernetes at least (like via Kustomize, Helm, Spinnaker, and general YAML template tooling), I’ve relied mostly on binding anything relevant from the manifest into environment variables.
> On Sep 11, 2023, at 6:10 AM, Piotr P. Karwasz <piotr.karw...@gmail.com> wrote: > > Hi Volkan, > > On Mon, 11 Sept 2023 at 10:00, Volkan Yazıcı <vol...@yazi.ci > <mailto:vol...@yazi.ci>> wrote: >> >> I would be in favor of deprecating the following modules in `2.x` and >> dropping them starting from `3.0.0`: >> >> 1. `log4j-jndi` (available only in `main`) – nobody should use JNDI >> anyway >> 2. `log4j-layout-jackson*` – `JsonTemplateLayout` succeeds `JsonLayout`, >> I doubt if anybody is using `XmlLayout`, nobody should use `YamlLayout` >> anyway >> 3. `log4j-gelf` (available only in `main`) – JTL offers the same >> functionality, we just need to add a `CompressingLayout` (see LOG4J2-3023) >> and a resolver template (i.e., `gelf.json`) >> 4. `log4j-jms` (available only in `main`) >> 5. `log4j-csv` (available only in `main`) >> 6. `log4j-jeromq` >> 7. `log4j-cassandra` >> 8. `log4j-smtp` >> 9. `log4j-jakarta-smtp` >> 10. `log4j-couchdb` >> 11. `log4j-taglib` >> 12. `log4j-mongodb3` >> 13. `log4j-spring*` – we should try to upstream these to Spring Boot, >> otherwise to their own `apache/logging-*` repository >> 14. `log4j-jdbc` >> 15. `log4j-kafka` – we should either hand this out to the community or, >> if not rewrite, revamp it. In its current state >> >> <https://issues.apache.org/jira/browse/LOG4J2-3173?filter=-2&jql=project%20%3D%20%22Log4j%202%22%20AND%20status%20%3D%20Open%20AND%20text%20~%20kafka>, >> it doesn't appear to be of production-grade quality. > > What about `kubernetes`, `docker` and `jpa`. Are these omissions intentional? > >> I don't want to derail the conversation at this stage, though I need to >> admit I have my reservations regarding the "please don't drop it because my >> employer uses it" argument. We can, preferably after the public feedback >> deadline, talk about it. > > Our employers are the Open Source equivalent of paying customers. If I > am not mistaken they allowed you to work on Log4j at one time or > another. > When Gary says "please don't drop..." I take it as a declaration that > he'll handle the issues filed against these modules (and he does do > it). > > Piotr
