Hello all. Those last days, I spent some times to deploy process to my client, using a Template. In the template, I have many InvokeHTTP processors, and some services related to the SSLContextService.
My client have 3 environments, and for two of them, I can not configure the SSLContextService, because I do not have to know password for keystore and trustore. So we decide to setup a SSLContextService at "root" level in NiFi once for all. Each time I deploy the Template, a new service is deployed (this was a previous question by someone here). I just have to delete the serice created during the template import. And then modify all processors. I was thinking of something than my help me and ask here if you think I could be nice to have it in future release (ideally in 1.9.3, if planned) We could have a sort of "proxy" for SSLContextService. The only property would be an instance of SSLContextService. And each call on the proxy will be a delegation to to "wrapped" instance. Like this, during deploy, I will just have to update the instance set on the "proxy". For other usage, we will be able to switch easly between SSL Context. The problem could be the implementation that may produce circular reference. But it is not our fault if user make things stupid. What do you think about that ? Regards Etienne Jouvin
