Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
cetic/helm-nifi apache/nifi docker environment variables
See original GitHub issueIs your feature request related to a problem? Please describe.
I am trying to pass in environment variables that the parent apache/nifi docker image supports, but seem to be disregarded by helm. Specifically NIFI_VARIABLE_REGISTRY_PROPERTIES which sets the value of the nifi.variable.registry.properties= property in the /opt/nifi/nifi-current/conf/nifi.properties file. Executing as a simple docker docker run -e NIFI_VARIABLE_REGISTRY_PROPERTIES=/opt/nifi/nifi-current/conf/custom/registry-secret.properties apache/nifi the value is set correctly from the entrypoint start.sh script
Describe the solution you’d like
Support parent Dockerfile env vars
Could also expose a value to override the nifi.variable.registry.properties property by adding a call to
prop_replace
prop_replace nifi.variable.registry.properties ${NIFI_VARIABLE_REGISTRY_PROPERTIES}
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Merged in 0.2.3.
@spencerdcarlson tell us if it is ok for you? Then, we can close this issue.
Hello @spencerdcarlson, I will have a look, already thank you!