Skip to content

Fix PI_LOGFILE handling in container logging config #210

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mr-ssd merged 1 commit into from
Sep 25, 2026
Merged

Fix PI_LOGFILE handling in container logging config #210

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions rootfs/usr/local/bin/configure_privacyidea.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,6 +112,27 @@ function generate_pi_config {

# Update the log level
sed -i -e "s/level: .*/level: ${PI_LOGLEVEL}/g" /opt/privacyidea/pi-logging.yml

# PI_LOGCONFIG uses this file handler, so PI_LOGFILE must also update its filename.
if [ -n "${PI_LOGFILE:-}" ]; then
python3 - <<'PY'
import json
import os
from pathlib import Path
import re

logging_config = Path("/opt/privacyidea/pi-logging.yml")
contents = logging_config.read_text()
contents, count = re.subn(
r"(?m)^([ \t]*filename:[ \t]*).*$",
lambda match: match.group(1) + json.dumps(os.environ["PI_LOGFILE"]),
contents,
)
if count != 1:
raise ValueError(f"Expected one log filename in {logging_config}, found {count}")
logging_config.write_text(contents)
PY
fi
}

# Function to perform pre-start tasks for PrivacyIDEA
Expand Down
Loading