[ https://issues.apache.org/jira/browse/NIFI-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376047#comment-17376047 ]
ASF subversion and git services commented on NIFI-8644: ------------------------------------------------------- Commit 6df07df3b2d2dbabeb279ac749ed45c37efd5d01 in nifi's branch refs/heads/main from Mark Payne [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=6df07df ] NIFI-8644: Introduced a notion of ParameterProviderDefinition - Refactored stateless to use this when creating a dataflow so that Parameter Provider implementations can be externalized into NARs. Also updated ExtensionDiscoveringManager such that callers are able to provide a new type of class to be discovered (e.g., ParameterProvider) so that the extensions will be automatically discovered - Put specific command-line overrides as highest precedence for parameter overrides - Make ParameterOverrideProvider valid by allowing for dynamically added parameters - Fixed bug in validation logic, added new system tests to verify proper handling of Required and Optional properties - Addressed review feedback and fixed some bugs. Also added system test to verify Parameter Providers are working as expected This closes #5113 Signed-off-by: David Handermann <exceptionfact...@apache.org> > Update Stateless so that a ParameterProviderDefinition is provided to > dataflow instead of ParameterProvider > ----------------------------------------------------------------------------------------------------------- > > Key: NIFI-8644 > URL: https://issues.apache.org/jira/browse/NIFI-8644 > Project: Apache NiFi > Issue Type: Improvement > Components: NiFi Stateless > Reporter: Mark Payne > Assignee: Mark Payne > Priority: Major > Fix For: 1.14.0 > > Time Spent: 2h 40m > Remaining Estimate: 0h > > Currently, when a stateless dataflow is created, a ParameterProvider is > supplied, which the engine can use to retrieve parameterized values for the > dataflow. > However, it will make sense going forward to allow for a ParameterProvider to > be defined outside of the scope of what is provided by default in the > stateless api. For example, there may be a desire to integrate with a a > secret store provided by a public cloud service, etc. Such a capability would > need to be encapsulated in a NAR instead of added to the root class path. > As such, we need to refactor the stateless api such that instead of providing > a ParameterProvider, we instead introduce a notion of a > ParameterProviderDefinition, and then include a List of > ParameterProviderDefinitions as part of the Dataflow Definition. > In this way, we can make the parameter retrieval far more flexible and > powerful. -- This message was sent by Atlassian Jira (v8.3.4#803005)