[GitHub] [nifi-minifi] GCHQ-NiFi commented on issue #167: MINIFI-424: Centralise Bootstrap config
GCHQ-NiFi commented on issue #167: MINIFI-424: Centralise Bootstrap config URL: https://github.com/apache/nifi-minifi/pull/167#issuecomment-530295586 @gruselglatz - No, this pull request just simplifies the transformConfigFile function. If this is merged in, it'll be easier to override flow settings using the bootstrap.conf (like the C2 SSL override). I've got a fix for the C2 SSL ready to go, it just relies on this pull request to get merged in first. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [nifi-minifi] GCHQ-NiFi commented on issue #167: MINIFI-424: Centralise Bootstrap config
GCHQ-NiFi commented on issue #167: MINIFI-424: Centralise Bootstrap config URL: https://github.com/apache/nifi-minifi/pull/167#issuecomment-527208530 @apiri Do you mind reviewing and seeing whether this is a better way of managing config transformation? Happy to make changes as needed! Going forward, we have other ideas which could take advantage of this - like passing in a boolean through the bootstrap.conf to hard code all processor SSL-Contexts to the minifi SSL config set in the bootstrap. We've had problems using SSL contexts when driving minifi with c2. As the nifi uses it's own SSL, this gets pulled across into minifi - which points to the wrong SSL details and can't start. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
