markobean opened a new pull request, #9116:
URL: https://github.com/apache/nifi/pull/9116
…he identical SSLContextService
rename StandardRestrictedSSLContextService to more concise name
RestrictedSSLContextService
<!-- Licensed to the Apache Software Foundation (ASF) under one or more -->
<!-- contributor license agreements. See the NOTICE file distributed with
-->
<!-- this work for additional information regarding copyright ownership. -->
<!-- The ASF licenses this file to You under the Apache License, Version 2.0
-->
<!-- (the "License"); you may not use this file except in compliance with -->
<!-- the License. You may obtain a copy of the License at -->
<!-- http://www.apache.org/licenses/LICENSE-2.0 -->
<!-- Unless required by applicable law or agreed to in writing, software -->
<!-- distributed under the License is distributed on an "AS IS" BASIS, -->
<!-- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied. -->
<!-- See the License for the specific language governing permissions and -->
<!-- limitations under the License. -->
# Summary
This PR may be somewhat controversial since it renames a heavily used
controller service which is clearly a breaking change. However, as we near the
release of 2.0.0, now is an appropriate time to make such a change.
It has always seemed odd that there is a service named
StandardRestrictedSSLContextService with both "standard" and "restricted" in
its name. Historically, there is logic to this naming. There is an interface,
RestrictedSSLContextService, which at one time was distinctly different from
the SSLContextService interface. However, the two are now identical.
This PR proposes to consolidate naming conventions. The
RestrictedSSLContextService interface has been removed. All references to it
have been updated to SSLContextService. Removing the interface also allows the
implementation name to become RestrictedSSLContextService rather than
StandardRestrictedSSLContextService.
There are no functional changes here. Rather this only updates the naming of
interfaces and corresponding implementations.
[NIFI-13587](https://issues.apache.org/jira/browse/NIFI-13587)
# Tracking
Please complete the following tracking steps prior to pull request creation.
### Issue Tracking
- [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue
created
### Pull Request Tracking
- [X] Pull Request title starts with Apache NiFi Jira issue number, such as
`NIFI-00000`
- [X] Pull Request commit message starts with Apache NiFi Jira issue number,
as such `NIFI-00000`
### Pull Request Formatting
- [X] Pull Request based on current revision of the `main` branch
- [X] Pull Request refers to a feature branch with one commit containing
changes
# Verification
Please indicate the verification steps performed prior to pull request
creation.
### Build
- [X] Build completed using `mvn clean install -P contrib-check`
- [X] JDK 21
### Licensing
- [ ] New dependencies are compatible with the [Apache License
2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License
Policy](https://www.apache.org/legal/resolved.html)
- [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE`
files
### Documentation
- [ ] Documentation formatting appears as expected in rendered files
--
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: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
