Hi, I was wondering about this too. We have the option to add a symlink which you just mentioned and I can do that if there are no argument against.
Also you can use the env var, when you do things through scripting: docker run --rm -ti --entrypoint bash apache/nifi:1.7.0 -c "echo \$NIFI_HOME" /opt/nifi/nifi-1.7.0 I'm not sure about the original reasons it was created this way. We may change to a version agnostic path with the next release and create a symlink with the version for backward compatibility. Peter On Tue, Jul 31, 2018 at 12:01 AM Jon Logan <[email protected]> wrote: > Hi, > > I was looking at utilizing the Docker distribution but was wondering if any > thought was given to making the paths version-agnostic? Specifically, the > conf folder is in /opt/nifi/nifi-1.7.1/conf. This would mean any > modifications we would make in a container or RPM would be tied to 1.7.1. > > I have seen other projects accomplish this with a symlink (ex. > /opt/nifi/latest -> opt/nifi/nifi-1.7.1), and think that approach might > work as well here? > > Is there a better approach? > > > Thanks! > Jon >
