[
https://issues.apache.org/jira/browse/NIFI-15909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18078785#comment-18078785
]
ASF subversion and git services commented on NIFI-15909:
--------------------------------------------------------
Commit 2feadfbe6543b5b2d622cf1e697b41dfc08f6dd5 in nifi's branch
refs/heads/main from Kevin Doran
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=2feadfbe654 ]
NIFI-15909 Resolve providerId from ConnectorConfigProvider values (#11209)
* NIFI-15909 Resolve providerId from ConnectorConfigProvider values
Resolve providerId on SECRET_REFERENCE entries returned by a
ConnectorConfigurationProvider
when only providerName is populated. The id is filled in only when the name
unambiguously
matches a single registered parameter provider; zero or ambiguous matches leave
providerId
null so the UI surfaces the SECRET_REFERENCE as invalid for re-configuration.
> Optionally resolve providerId by name when loading connector config secret
> references from a ConnectorConfigurationProvider
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-15909
> URL: https://issues.apache.org/jira/browse/NIFI-15909
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Kevin Doran
> Assignee: Kevin Doran
> Priority: Minor
> Time Spent: 50m
> Remaining Estimate: 0h
>
> A {{ConnectorConfigurationProvider}} may return SECRET_REFERENCE entries with
> only {{providerName}} populated, since {{providerId}} is a runtime-assigned
> UUID that the provider has no way to know about ahead of time. This change
> adds a resolution step in {{StandardConnectorRepository}} that runs at the
> two boundaries where provider-sourced configuration enters the framework
> ({{{}load(...){}}} results consumed by {{{}syncFromProvider{}}}, and
> {{getSyncDirective(...)}} results consumed by {{{}syncConnector{}}}): for
> each SECRET_REFERENCE with a null {{{}providerId{}}}, the framework looks up
> the named parameter provider via {{FlowManager.getAllParameterProviders()}}
> and fills in the id only when the name unambiguously identifies a single
> provider. If zero or multiple parameter providers share the name,
> {{providerId}} is left null so the UI can surface the SECRET_REFERENCE as
> invalid and prompt the user to re-configure it explicitly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
