[
https://issues.apache.org/jira/browse/KNOX-3511?focusedWorklogId=1047018&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1047018
]
ASF GitHub Bot logged work on KNOX-3511:
----------------------------------------
Author: ASF GitHub Bot
Created on: 12/Oct/26 14:02
Start Date: 12/Oct/26 14:02
Worklog Time Spent: 10m
Work Description: hanicz merged PR #1450:
URL: https://github.com/apache/knox/pull/1450
Issue Time Tracking
-------------------
Worklog Id: (was: 1047018)
Time Spent: 0.5h (was: 20m)
> Gateway ignores gateway-reloadable.xml if the file did not exist at startup
> ---------------------------------------------------------------------------
>
> Key: KNOX-3511
> URL: https://issues.apache.org/jira/browse/KNOX-3511
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 3.1.0
> Reporter: Tamás Hanicz
> Assignee: Tamás Hanicz
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Description:
> GatewayConfigImpl registers gateway-reloadable.xml as a configuration
> resource only if the file exists when the gateway starts (loadConfigFile
> checks f.exists() before addResource). The refresh loop in
> GatewayServer.refreshGatewayConfig still notices when the file is created
> later, calls reloadConfiguration(), logs "Refreshed gateway config" and
> notifies every GatewayConfigChangeListener. But reloadConfiguration()
> re-reads only the resources registered at startup, so none of the new file's
> properties take effect. For example, gateway.ldap.enabled=true leaves
> isLDAPEnabled() false and the embedded LDAP never starts. Nothing logs a
> warning or error. Later edits to the file are ignored too, until the gateway
> restarts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
