Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.8.0
-
None
-
e.g. docker, docker-compose
Description
Currently when starting the official docker image it auto generates the nifi.properties file using environment variables. This is fine if you are using a configuration that is supported by nifi but makes it impossible to overwrite the nifi.properties file manually (e.g. by mounting it via docker-compose.yml).
It's nice to make the configuration easier but the project may grow and additional configurations are (besides 'ldap', 'tls') will be needed. It seems to me that the configuration file (nifi.properties) should handle this.
My proposal is to simply and an environment flag that allows to turn off the generation by any other environment variables. This makes it possible to just mount the nifi.properties file directly (for more complex configurations).
Example:
nifi:
image: apache/nifi:latest
ports:
- 9443:9443 # Secured HTTP Web Port
volumes:
- "${PWD}/nifi.properties:/opt/nifi/nifi-current/conf/nifi.properties"
environment:
- NIFI_AUTOGEN_PROPERTIES_FILE=0
Workaround: As a workaround the user could currently overwrite the startup command and just manually start the nifi instance.
To add to this issue:
It is odd that apache nifi only allows OIDC with https enabled. If someone would try to do ssl termination via a nginx or similiar (in front of nifi) he would not be able to use OIDC.