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 2023/02/22 21:28:00 UTC

[jira] [Assigned] (NIFI-9003) Framework implementation of ParameterProvider

     [ https://issues.apache.org/jira/browse/NIFI-9003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Payne reassigned NIFI-9003:
--------------------------------

    Assignee: Mark Payne  (was: Joe Gresock)

> Framework implementation of ParameterProvider
> ---------------------------------------------
>
>                 Key: NIFI-9003
>                 URL: https://issues.apache.org/jira/browse/NIFI-9003
>             Project: Apache NiFi
>          Issue Type: Sub-task
>            Reporter: Joe Gresock
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 1.18.0
>
>         Attachments: Parameter_Providers.json, param-providers.sh
>
>          Time Spent: 3h 50m
>  Remaining Estimate: 0h
>
> This should be the core implementation, including:
> * ParameterProvider interface in the core framework API
> * Addition of sensitive/non-sensitive ParameterProviders to ParameterContext interface
> * Implementation of StandardParameterProvider in core framework
> * Update to StandardParameterContext for above interface changes
> * Serialization of ParameterProviders in flow.xml.gz and flow definition JSON
> * Fetch Parameters operation and REST endpoint (ensure the correct policies apply)
> With a test implementation of a ParameterProvider, this should be enough to exercise the new framework without UI or CLI changes, since a ParameterProvider could be entered manually in a flow definition and have its values fetched using the REST API.



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