feat(config): expose log.conditions via OWNCLOUD_LOG_CONDITIONS

[DeepDiver1975]

What

Exposes ownCloud core's log.conditions config value through a new OWNCLOUD_LOG_CONDITIONS environment variable, parsed in overlay/etc/templates/config.php for all three versions (v20.04, v22.04, v24.04).

Why

log.conditions (documented in core's config.apps.sample.php) is a list of condition maps mixing scalar and array values:

'log.conditions' => [
    [
        'shared_secret' => '...',   // string
        'users'         => ['u1'],  // string[]
        'apps'          => ['a1'],  // string[]
        'logfile'       => '/x.log',// string
        'loglevel'      => 0,       // int
    ],
],

The flat env-var idioms already used in config.php (explode() for flat lists, parse_str() for a single key=value map) cannot represent a list of maps with nested arrays, so this value previously had no env-var equivalent in the image.

How

A single JSON-encoded env var is the faithful representation:

if (getenv('OWNCLOUD_LOG_CONDITIONS') != '') {
  $logConditions = json_decode(getenv('OWNCLOUD_LOG_CONDITIONS'), true);
  if (is_array($logConditions)) {
    $config['log.conditions'] = $logConditions;
  }
}

Example:

OWNCLOUD_LOG_CONDITIONS='[{"apps":["files_external"],"loglevel":0,"logfile":"/var/log/oc-debug.log"}]'

The is_array() guard makes malformed JSON a no-op (key left unset, core falls back to default) rather than a fatal config-generation error.

Testing

• php -l clean on all three files.
• Functional test of getConfigFromEnv() covering: valid single condition (all five fields, types preserved), valid multi-condition list, malformed JSON (ignored), and unset (key absent).

🤖 Generated with Claude Code

[mmattel]

Docs to ENVIRONMENT.md is missing