[jira] [Updated] (NIFIREG-81) Variable Registry properties that are expected for a versioned Flow should be tracked

["Bryan Bende (JIRA)" <ji...@apache.org>]

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

Bryan Bende updated NIFIREG-81:
-------------------------------
    Affects Version/s: 0.1.0

> Variable Registry properties that are expected for a versioned Flow should be tracked 
> --------------------------------------------------------------------------------------
>
>                 Key: NIFIREG-81
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-81
>             Project: NiFi Registry
>          Issue Type: Improvement
>    Affects Versions: 0.1.0
>            Reporter: Joseph Percivall
>
> As a user, pulling down a new versioned flow, I'd like to know which properties are expected in my NiFi's Variable Registry to run the flow. By explicitly calling these out I can more easily configure and understand the flow on deployment. Also, would facilitate maintainability. 
> An easy example of a typical flow that would utilize this is one that relies on an external source which is configured per environment (SSL file paths, Web service URL, etc.).
> This could also pave the way to set "default" variables within a Registry instance and elsewhere.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)