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

Pierre Villard updated NIFI-14700:
----------------------------------
    Status: Patch Available  (was: Open)

> Option to ignore parameter value changes in git registry clients
> ----------------------------------------------------------------
>
>                 Key: NIFI-14700
>                 URL: https://issues.apache.org/jira/browse/NIFI-14700
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Pierre Villard
>            Assignee: Pierre Villard
>            Priority: Major
>
> In NIFI-14555 we added the option to commit a new versioned flow with empty 
> values for all parameters. This is a good strategy in case you want to make 
> sure that you're not inadvertently committing a new version that would 
> contain some parameter values that are specific to a lower environment.
> However this strategy is not great when you have parameters where you want to 
> specify a default value. In such a case, and when using the strategy 
> implemented in NIFI-14555, you'd lose the default values for your parameters 
> when you commit a new version.
> This JIRA is to add a new strategy allowing to commit a version where any 
> already existing parameter is ignored. It means that we change the version we 
> are committing by copying the existing values of the existing parameters into 
> the new version. This is particularly useful as changing the value of a 
> parameter is not considered as a local change so it can be confusing for a 
> user to commit a new version where it is also including parameter value 
> changes.
> This is not a perfect solution because this strategy does not allow the user 
> to change a default value that would have been set previously. But in that 
> case the user can switch between the strategies at the registry client level 
> to execute the right sequence of steps to get the expected end result.



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

Reply via email to