[jira] [Comment Edited] (NIFI-8907) Variable Registry properties that are expected for a versioned Flow should be tracked

["John Wise (Jira)" <ji...@apache.org>]

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

John Wise edited comment on NIFI-8907 at 1/30/23 4:13 PM:
----------------------------------------------------------

This is counter to what most users actually want.  We set "global" variables at the root level of our canvases for things like cluster/region-specific proxy servers, endpoint URLs, and the like.  We *don't* want those tracked as changes, because they're not applicable to every cluster, and because it breaks the flows on those clusters.  Numerous process groups are now marked as "changed" because variables are getting pulled into lower-level process groups.  We have many reusable process groups deployed across dozens of clusters, and if someone checks in a "changed" process group with those variables, they then get added to every other cluster when they're updated, which breaks those flows everywhere else.

Saving variables in the Registry from a nested process group should be *{*}optional{*}*, not the default behavior.


was (Author: john.wise):
This is counter to what most users actually want.  We set "global" variables at the root level of our canvases for things like cluster-specific proxy servers, endpoint URLs, and the like.  Most of those are specific to a given cluster or region, which we *don't* want tracked as changes, because it breaks our Registry processes.  Numerous process groups are now marked as "changed" because variables are getting pulled into lower-level process groups.  We have numerous reusable process groups deployed across dozens of clusters, and if someone checks in a "changed" process group with those variables, they then get added to every other cluster when they're updated, which breaks those flows everywhere else.

Saving variables in the Registry from a nested process group should be **optional**, not the default behavior.

> Variable Registry properties that are expected for a versioned Flow should be tracked 
> --------------------------------------------------------------------------------------
>
>                 Key: NIFI-8907
>                 URL: https://issues.apache.org/jira/browse/NIFI-8907
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: NiFi Registry
>            Reporter: Joe Percivall
>            Priority: Major
>
> 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
(v8.20.10#820010)