You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "peng_lp (Jira)" <ji...@apache.org> on 2020/01/09 06:32:00 UTC
[jira] [Comment Edited] (NIFI-6995) InvokeHTTP processor Auth user
name didn't support registry variable
[ https://issues.apache.org/jira/browse/NIFI-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17011473#comment-17011473 ]
peng_lp edited comment on NIFI-6995 at 1/9/20 6:31 AM:
-------------------------------------------------------
thanks Tony for mentioning this , we have variables to make the deployment across different staging environment, we also see lot's of other Processors NOT support EL for while from the source code standard , it's already well defined. Team can you please improve this ?(y)(y)
was (Author: peng_lp):
thanks Tony for mentioning this , we have variables to make the deployment across different staging environment, we also see lot's of other Processors DOES NOT support EL for while from the source code standard , it's already well defined. Team can you please improve this ?(y)(y)
> InvokeHTTP processor Auth user name didn't support registry variable
> --------------------------------------------------------------------
>
> Key: NIFI-6995
> URL: https://issues.apache.org/jira/browse/NIFI-6995
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.9.2
> Reporter: tony wang
> Priority: Minor
>
> InvokeHTTP processor property (Basic Authentication Username) didn't support registry variable and any changes to this value will impact the nifi registry version management. It's hard to managed it cross multiple environment in case different user id used.
> It will be better ether mark this property as secure or support registry variable
--
This message was sent by Atlassian Jira
(v8.3.4#803005)