You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2023/10/19 13:41:00 UTC
[jira] [Updated] (NIFI-12243) Refactor encrypt-config Command Implementation
[ https://issues.apache.org/jira/browse/NIFI-12243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Handermann updated NIFI-12243:
------------------------------------
Status: Patch Available (was: In Progress)
> 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: 10m
> 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)