[ https://issues.apache.org/jira/browse/NIFI-5119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16452889#comment-16452889 ]
ASF GitHub Bot commented on NIFI-5119: -------------------------------------- Github user jomach closed the pull request at: https://github.com/apache/nifi/pull/2656 > Pulling changes from Registry does not respect sensitive Informations on > Destination > ------------------------------------------------------------------------------------ > > Key: NIFI-5119 > URL: https://issues.apache.org/jira/browse/NIFI-5119 > Project: Apache NiFi > Issue Type: Bug > Components: Variable Registry > Affects Versions: 1.5.0, 1.6.0 > Environment: all > Reporter: Jorge Machado > Priority: Major > Fix For: 1.7.0 > > > When pulling changes from registry if a sensitive variable is set then it > gets reset to its default. > I have found out a use case that destroys the complete concept of the > Registry. > # Setup a flow with a sensitive field on Nifi Server A. > # Push that to Registry > # Pull the Flow in Nifi Server B. (this is expected to be reseted because > is the first time) > # Make changes on Nifi Server B and Push > # Pull the changes from Nifi Server A. > > On Step 5 the sensitive Information from Nifi Server A get's deleted. > This breaks the whole concept IMHO. > Relates to : NIFI-5028 -- This message was sent by Atlassian JIRA (v7.6.3#76005)