exceptionfactory opened a new pull request #5650:
URL: https://github.com/apache/nifi/pull/5650
#### Description of PR
NIFI-9438 Refactors the `nifi-sensitive-property-provider` module to the
following separate modules based on various types of providers:
- nifi-property-protection-api
- nifi-property-protection-factory
- nifi-property-protection-aws
- nifi-property-protection-azure
- nifi-property-protection-cipher
- nifi-property-protection-gcp
- nifi-property-protection-hashicorp
- nifi-property-protection-shared
This approach allows for more specific dependency management within
individual providers while still supporting unified access to provider
implementations through the `nifi-property-protection-factory` module.
Refactoring into separate modules required some clarification and
simplification of the `SensitivePropertyProvider` interface as well as the
`StandardSensitivePropertyProviderFactory`. Instead of having a direct
association between the command line argument values supported in the
`PropertyProtectionScheme` enumeration, the `nifi-property-protection-api`
module introduces a `ProtectionSchemeResolver` interface. The
`StandardProtectionSchemeResolver` encapsulates resolution from command line
arguments to `ProtectionScheme` instances. This approach decouples the
`SensitivePropertyProvider` implementation from the `PropertyProtectionScheme`
enumeration and instead relies on registering the protection scheme path
exposed through the `SensitivePropertyProvider.getIdentifierKey()` method.
Additional changes include renaming `AESSensitivePropertyProvider` to
`AesGcmSensitivePropertyProvider` as well as removing and streamlining a number
of unit tests that performed duplicative testing of AES-GCM cipher operations.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [X] Does your PR title start with **NIFI-XXXX** where XXXX is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [X] Has your PR been rebased against the latest commit within the target
branch (typically `main`)?
- [X] Is your initial contribution a single, squashed commit? _Additional
commits in response to PR reviewer feedback should be made on this branch and
pushed to allow change tracking. Do not `squash` or use `--force` when pushing
to allow for clean monitoring of changes._
### For code changes:
- [X] Have you ensured that the full suite of tests is executed via `mvn
-Pcontrib-check clean install` at the root `nifi` folder?
- [X] Have you written or updated unit tests to verify your changes?
- [X] Have you verified that the full build is successful on JDK 8?
- [X] Have you verified that the full build is successful on JDK 11?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE` file, including the main
`LICENSE` file under `nifi-assembly`?
- [ ] If applicable, have you updated the `NOTICE` file, including the main
`NOTICE` file found under `nifi-assembly`?
- [ ] If adding new Properties, have you added `.displayName` in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in which
it is rendered?
### Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for
build issues and submit an update to your PR as soon as possible.
--
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]
