[
https://issues.apache.org/jira/browse/NIFI-6283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominik Falkner updated NIFI-6283:
----------------------------------
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:
{code:java}
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
{code}
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.
was:
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:
{code:java}
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
{code}
Workaround: As a workaround the user could currently overwrite the startup
command and just manually start the nifi instance.
> Support Different Types of Docker Deployments
> ---------------------------------------------
>
> Key: NIFI-6283
> URL: https://issues.apache.org/jira/browse/NIFI-6283
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Docker, Tools and Build
> Affects Versions: 1.8.0
> Environment: e.g. docker, docker-compose
> Reporter: Dominik Falkner
> Priority: Major
> Labels: easyfix
>
> 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:
> {code:java}
> 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
> {code}
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
