[
https://issues.apache.org/jira/browse/NIFI-13587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17869668#comment-17869668
]
Mark Bean commented on NIFI-13587:
----------------------------------
This may be related to NIFI-13600 which would allow name changes without it
breaking existing flows.
> Refactor StandardRestrictedSSLContextService naming convention
> --------------------------------------------------------------
>
> Key: NIFI-13587
> URL: https://issues.apache.org/jira/browse/NIFI-13587
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 2.0.0-M4
> Reporter: Mark Bean
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> In the past, there was a purpose to having a RestrictedSSLContextService
> interface which was different from SSLContextService. However, changes have
> made these two interfaces identical.
> Suggest removing RestrictedSSLContextService and update references to use
> SSLContextService. Similarly, the currently named controller service,
> StandardRestrictedSSLContextService can be refactored to
> RestrictedSSLContextService. It always seemed odd that the controller service
> was named with both "standard" and "restricted".
> This is a very commonly used controller service and renaming it will have
> obvious implications for flow definitions. However, such a breaking change
> would be appropriate at the transition to version 2.0.0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
