The GitHub Actions job "Build" on texera.git/main has failed.
Run started by GitHub user bobbai00 (triggered by bobbai00).

Head commit for run:
e908c60de85ec42fa3be4d8e82c9fcc96e970d0b / Jiadong Bai 
<[email protected]>
chore: make service log levels configurable via TEXERA_SERVICE_LOG_LEVEL (#4244)

### What changes were proposed in this PR?

This PR makes log levels configurable across all 7 Texera services via a
single `TEXERA_SERVICE_LOG_LEVEL` environment variable, defaulting to
`INFO`.

Changes include:
- Enable Dropwizard's `EnvironmentVariableSubstitutor` in each service's
`initialize()` to support `${VAR:-default}` syntax in YAML configs
- Replace all hardcoded `level: INFO` with `level:
${TEXERA_SERVICE_LOG_LEVEL:-INFO}` in Dropwizard YAML configs,
logback.xml files, and Pekko cluster.conf
- Disable Dropwizard's built-in `requestLog` console appender (which
uses a separate logback-access pipeline not controllable by standard log
levels) and replace it with a servlet filter that routes HTTP access
logs through SLF4J at INFO level
- Extract shared `RequestLoggingFilter` class in `common/auth` for the 4
DW 4.x services; DW 1.3.x services use inline filters with a TODO to
migrate after Dropwizard upgrade
- Add `TEXERA_SERVICE_LOG_LEVEL=INFO` to `bin/single-node/.env`

### Any related issues, documentation, discussions?

Closes #4243

### How was this PR tested?

- Manually set `TEXERA_SERVICE_LOG_LEVEL=ERROR` and verified only
error-level logs appear (no HTTP access logs, no INFO messages)
- Manually set `TEXERA_SERVICE_LOG_LEVEL=INFO` (or left unset) and
verified normal logging behavior including HTTP access logs

### Was this PR authored or co-authored using generative AI tooling?

Generated-by: Claude Code (Claude Opus 4.6)

Report URL: https://github.com/apache/texera/actions/runs/22513463458

With regards,
GitHub Actions via GitBox

Reply via email to