[
https://issues.apache.org/jira/browse/NIFI-13587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Bean updated NIFI-13587:
-----------------------------
Description:
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.
was:
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".
> 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
>
> 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)
