You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "James Sevener (Jira)" <ji...@apache.org> on 2021/02/09 03:29:00 UTC
[jira] [Updated] (NIFI-6980) NiFi can't use symlinks for some conf
files
[ https://issues.apache.org/jira/browse/NIFI-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Sevener updated NIFI-6980:
--------------------------------
Affects Version/s: 1.11.4
1.12.1
> NiFi can't use symlinks for some conf files
> -------------------------------------------
>
> Key: NIFI-6980
> URL: https://issues.apache.org/jira/browse/NIFI-6980
> Project: Apache NiFi
> Issue Type: Bug
> Components: Docker
> Affects Versions: 1.10.0, 1.9.2, 1.11.4, 1.12.1
> Environment: Tested with docker, though this probably affects other environments as well.
> Reporter: James Sevener
> Priority: Minor
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Some files lend themselves to being ephemeral instead of persistent, but live in the conf directory. Logback.xml is a great example, and moving the file to the container and then symlinking works. This doesn't work for any files that the various sh scripts call the prop_replace function in common.sh as the sed call doesn't include --follow-symlinks
--
This message was sent by Atlassian Jira
(v8.3.4#803005)