[
https://issues.apache.org/jira/browse/NIFI-12243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778313#comment-17778313
]
ASF subversion and git services commented on NIFI-12243:
--------------------------------------------------------
Commit f352857e42e7c9590471ae07eeb4a2bbf9ef981c in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=f352857e42 ]
NIFI-12243 Refactored encrypt-config using picocli
- Replaced Groovy implementation with Java classes
- Added StandardEncryptConfig and RegistryEncryptConfig command implementations
- Added FileTransformer interface with implementations for configuration files
- Changed -A to -u for output authorizers.xml when targeting Registry
- Removed --newFlowProvider option not used
- Removed --translateCli option
- Removed --decrypt option
Signed-off-by: Joe Gresock <[email protected]>
This closes #7901.
> Refactor encrypt-config Command Implementation
> ----------------------------------------------
>
> Key: NIFI-12243
> URL: https://issues.apache.org/jira/browse/NIFI-12243
> Project: Apache NiFi
> Issue Type: Improvement
> Components: NiFi Registry, Tools and Build
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Fix For: 2.latest
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The {{encrypt-config}} command in {{nifi-toolkit-encrypt-config}} supports
> protection of sensitive properties in multiple application configuration
> files. The current implementation supports NiFi and NiFi Registry with
> similar capabilities.
> The existing implementation is written in Groovy and includes some amount of
> duplication between operating modes.
> The command supports capabilities unique to NiFi for protection for specific
> property values in application properties and flow configuration files.
> The {{encrypt-config}} command components should be refactored using the
> [picocli|https://picocli.info/] framework to streamline the implementation.
> This refactoring should focus on supporting existing command arguments to
> provide compatibility with existing usage patterns. Separate efforts could
> consider a redesigned approach with different arguments and sub-commands, but
> refactoring the current implementation will provide a more maintainable
> solution.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
