Toivo,
I think there needs to be some improvements around variables &
sensitive property handling, but it is a challenging situation.
Some things you could investigate with the current capabilities..
- With the registry scenario, you could define a DBCPConnectionPool at
the root process group
Hi Bryan,
We start using Registry soon anyway, so this is useful info.
But it would be event better when we don’t need to enter passwords manually
each time we deploy template.
Any ideas how to do this?
Thank you
Toivo
--
Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
You may want to consider moving from templates to NiFi Registry for
your deployment approach. The idea of this approach is that your flow
will get saved to registry with no sensitive values, when you import
the flow to the next environment you enter the sensitive values there
the first time and
Hi Bryan,
>> Are you saying you are trying to externalize the value outside the
>> w and keep it encrypted somewhere else?
Yes, exactly. We have different passwords on different environments (dev,
test, production).
After development flow (using template currently) will be deployed to test
Toivo,
The password property on DBCPConnectionPool is a "sensitive" property
which means it is already encrypted in the flow.xml.gz using
nifi.sensitive.props.key.
Are you saying you are trying to externalize the value outside the
flow and keep it encrypted somewhere else?
-Bryan
On Mon, Mar
Hi,
I need to encrypt DBCPConnectionPool password.
I have working decryption code.
Problem is how to make decrypted password available to DBCPConnectionPool.
I thought to use expression language and JVM System Property’s.
DBCPConnectionPool is capable to read System property value.
But how to
