pvillard31 commented on PR #7965:
URL: https://github.com/apache/nifi/pull/7965#issuecomment-1788239534

   I feel like the reported problem could happen in any implementation of the 
Registry Client, not just this one. Instead of taking this approach that is 
quite specific to the SSL controller service, should we consider adding 
something at the framework level to trigger a "refresh" method anytime the 
configuration of the component is changed? It would then be up to the component 
to implement whatever makes sense in this refresh method. Thoughts?
   
   Note: I'm fine with this approach to solve the immediate problem but I feel 
like we could have a more generic approach in case there are some other 
implementations of the Registry Client interface.


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to