You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Jorge Machado (JIRA)" <ji...@apache.org> on 2018/04/25 09:55:00 UTC

[jira] [Commented] (NIFI-5028) CLI - Add a command to list sensitive properties to set

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

Jorge Machado commented on NIFI-5028:
-------------------------------------

Actually it would be nice that we could detect if a sensitive field has a variable set. If yes then then we push this. I have found out a use case that destroys the complete concept of the Registry. 

 

 1- Setup a flow with a EL on the sensitive field.

 2- push that to Registry

3 - pull the Flow in another Nifi system.  

 

It will automatically set the sensitive information to not set, regardless if it was set or not. 

This breaks the whole concept IMHO.

> CLI - Add a command to list sensitive properties to set
> -------------------------------------------------------
>
>                 Key: NIFI-5028
>                 URL: https://issues.apache.org/jira/browse/NIFI-5028
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Tools and Build
>            Reporter: Pierre Villard
>            Priority: Major
>
> When versioning a process group, all the sensitives values will be removed for security reasons. When importing the versioned process group for the first time in the final environment, it'll be necessary to manually set the value of the sensitive properties (or the newly added sensitive properties in case of version update).
> It'd be helpful to have a command listing all the sensitives properties contained in the process group that need to be set. Additionally a command allowing the user to set the property would be useful to automate workflow deployments.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)