[
https://issues.apache.org/jira/browse/NIFI-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585177#comment-16585177
]
Corey Fritz edited comment on NIFI-5536 at 8/19/18 3:54 PM:
------------------------------------------------------------
Unfortunately, hardcoding the password in the versioned flow doesn’t work for
us, because we’re deploying the flows to environments (dev, qa, uat, prod) that
have different passwords. We’ve been using this same approach for configuring
passwords for DBCPConnectionPools and RedisConnectionPools.
was (Author: snagafritz):
Unfortunately, hardcoding the password in the versioned flow doesn’t work for
us, because we’re deploying the flows to environments (dev, qa, uat, prod) that
have different passwords.
> Add EL support for password on AMQP processors
> ----------------------------------------------
>
> Key: NIFI-5536
> URL: https://issues.apache.org/jira/browse/NIFI-5536
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Corey Fritz
> Priority: Major
>
> NIFI-5489 added EL support to the host, port, virtual host, and user
> properties of AMQP processors. Not sure why password was not included. We
> have a use case where sensitive values (passwords) are set as environment
> variables on our Docker containers and then those variables are referenced by
> name using EL expressions in our processors and controller services. Flow
> authors then have no need or means to know what those sensitive values are.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
