#7410 bug: File with log are generated even if configuration doesn't include file handler Issue created by Bakrog Meltano Version 2.16.1 Python Version 3.11 Bug scope CLI (options, error messages, logging, etc.) Operating System Debian - Docker - python:3.11-slim Description Currently I have the following log configuration only declaring a console handler and disabling existing logs but even so running my job still generates an log file at

.meltano/logs/<job_name>/<id>/etl.log

. version: 1 disable_existing_loggers: true formatters: json: (): meltano.core.logging.json_formatter handlers: console: class: logging.StreamHandler formatter: json stream: "ext://sys.stderr" root: level: INFO propagate: yes handlers: [console] This generation of log files can lead to a failure when the process is running on kubernetes because of not enough ephemeral-storage resource. If possible the best scenario would be just send the logs to console and let the container log listener process ship them to the log aggregator. But as I said before even explicit disabling existing logs and only declaring a console handler doesn't disable the generation of log files. Code No response meltano/meltano