[jira] [Commented] (NIFI-12220) Allow migrating properties to Controller Services

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-12220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779111#comment-17779111 ] 

ASF subversion and git services commented on NIFI-12220:
--------------------------------------------------------

Commit a44b63325244a042feb4df3a8f8bb7c2c5b7668d in nifi's branch refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a44b633252 ]

NIFI-12220 Added ability to create Controller Services from migrateProperties

- Added ability to get raw property values from PropertyConfiguration instead of just effective values
- Updated TestRunner to allow for testing these migration methods
- Auto-enable newly created controller services if they are valid
- Eliminated Proxy properties in all AWS processors and instead just make use of the Proxy Configuration controller service
- Eliminated authentication properties from AWS processors and migrated all processors to using Controller Service or authentication

This closes #7874

Signed-off-by: David Handermann <ex...@apache.org>


> Allow migrating properties to Controller Services
> -------------------------------------------------
>
>                 Key: NIFI-12220
>                 URL: https://issues.apache.org/jira/browse/NIFI-12220
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework, Extensions
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 2.latest
>
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> In NIFI-12139, we allowed processors, controller services, and reporting tasks to evolve over time by allowing properties to be renamed/removed and allowing Relationships to be renamed, split, etc.
> However, there's a common pattern that we see that NIFI-12139 doesn't account for: the ability to move properties to Controller Services. This happens commonly, especially with authentication types of properties. For example, in the AWS processors, we started with a "Secret Key" and an "Access Key ID." But over time, we needed other authentication methods. Eventually a Controller Service was created for performing authentication, and it allows for many different authentication options.
> But we cannot simply remove the Access Key ID and Secret Key properties. Their values need to be transferred to a Controller Service - one that likely doesn't exist yet. We need the ability to have the processor create that controller service and configure it in its migrateProperties method. And then remove the properties from the processor.
> The exact same thing has happened with the AWS Processors' proxy configuration. And something similar with Kerberos authentication services. And others.
> We need to allow for a seamless migration that supports creating Controller Services and configuring them, such that we can remove things like Access Key ID / Secret Key from the processor configuration and have the processors continue to function just as they did before.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)