You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mark Payne (Jira)" <ji...@apache.org> on 2021/06/04 15:51:00 UTC
[jira] [Updated] (NIFI-8644) Update Stateless so that a
ParameterProviderDefinition is provided to dataflow instead of
ParameterProvider
[ https://issues.apache.org/jira/browse/NIFI-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Payne updated NIFI-8644:
-----------------------------
Fix Version/s: 1.14.0
Status: Patch Available (was: Open)
> 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: 10m
> 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)