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

John Wise commented on NIFI-8907:
---------------------------------

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)

Reply via email to