You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joseph Gresock (Jira)" <ji...@apache.org> on 2021/09/06 11:19:00 UTC

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

    [ https://issues.apache.org/jira/browse/NIFI-9003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17409951#comment-17409951 ] 

Joseph Gresock edited comment on NIFI-9003 at 9/6/21, 11:18 AM:
----------------------------------------------------------------

Added a script that demonstrates basic parameter provider usage.  Steps to execute:
# Deploy PR branch
# Import the Parameter_Providers.json flow definition (attached)
# Assuming nifi-toolkit cli session is set up to talk to the nifi instance, run ./param-providers.sh (or ./param-providers.sh true to clean up any providers/contexts created during the script prior to completion)


was (Author: jgresock):
Added a script that demonstrates basic parameter provider usage.  Steps to execute:
# Deploy PR branch (forthcoming)
# Import the Parameter_Providers.json flow definition (attached)
# Assuming nifi-toolkit cli session is set up to talk to the nifi instance, run ./param-providers.sh (or ./param-providers.sh true to clean up any providers/contexts created during the script prior to completion)

> Framework implementation of ParameterProvider
> ---------------------------------------------
>
>                 Key: NIFI-9003
>                 URL: https://issues.apache.org/jira/browse/NIFI-9003
>             Project: Apache NiFi
>          Issue Type: Sub-task
>            Reporter: Joseph Gresock
>            Assignee: Joseph Gresock
>            Priority: Major
>         Attachments: Parameter_Providers.json, param-providers.sh
>
>          Time Spent: 10m
>  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.3.4#803005)