[
https://issues.apache.org/jira/browse/NIFI-8943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-8943:
-----------------------------------
Status: Patch Available (was: Open)
Thanks for reporting this issue and describing the problem [~Buhr]! I have
submitted a pull request updating the Docker start script to avoid replacing
the {{nifi.sensitive.props.key}} property when the environment variable is not
specified.
> NiFi Docker Image 14.0
> ----------------------
>
> Key: NIFI-8943
> URL: https://issues.apache.org/jira/browse/NIFI-8943
> Project: Apache NiFi
> Issue Type: Bug
> Components: Docker
> Affects Versions: 1.14.0
> Environment: Docker Running on Mac OS
> Reporter: Brendan
> Assignee: David Handermann
> Priority: Critical
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The new docker image has a bug in its start.sh file
> on creation of the docker container the "nifi.sensitive.props.key" value gets
> set
> on shutdown of the container and startup which triggers the
> "/opt/nifi/scripts/start.sh" file this gets overwritten because in the
> "/opt/nifi/scripts/start.sh" file of the docker setup this value gets set to
> blank making bootup fail due to the "nifi.sensitive.props.key" being required.
> This line exists in the start.sh file
> {code:bash}
> prop_replace 'nifi.sensitive.props.key' "${NIFI_SENSITIVE_PROPS_KEY:-}"
> {code}
> I suspect the intent was to have it replaced with a configurable parameter
> but the outcome is it currently breaks the Docker image after reboot and its
> a costly one.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
