You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Kevin Doran (Jira)" <ji...@apache.org> on 2026/05/05 17:54:00 UTC

[jira] [Created] (NIFI-15909) Optionally resolve providerId by name when loading connector config secret references from a ConnectorConfigurationProvider

Kevin Doran created NIFI-15909:
----------------------------------

             Summary: 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


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)