mirror of https://github.com/apache/nifi.git
NIFI-6907 Added nifi.bootstrap.sensitive.key to Bootstrap Properties section in Admin Guide
Signed-off-by: Pierre Villard <pierre.villard.fr@gmail.com> This closes #3927.
This commit is contained in:
parent
ec5bc7ea7a
commit
7f49c6b76a
|
@ -2147,6 +2147,9 @@ take effect only after NiFi has been stopped and restarted.
|
|||
|`java.arg.N`|Any number of JVM arguments can be passed to the NiFi JVM when the process is started. These arguments are defined by adding properties to _bootstrap.conf_ that
|
||||
begin with `java.arg.`. The rest of the property name is not relevant, other than to differentiate property names, and will be ignored. The default includes
|
||||
properties for minimum and maximum Java Heap size, the garbage collector to use, etc.
|
||||
|`nifi.bootstrap.sensitive.key`|The master key in hexadecimal format for encrypted sensitive configuration values. When NiFi is started, the master key is used to decrypt sensitive values from the _nifi.properties_ file into memory for later use.
|
||||
|
||||
The Encrypt-Config Tool can be used to specify the master key, encrypt sensitive values in _nifi.properties_ and update _bootstrap.conf_. See the <<toolkit-guide.adoc#encrypt_config_tool,NiFi Toolkit Guide>> for an example.
|
||||
|`notification.services.file`|When NiFi is started, or stopped, or when the Bootstrap detects that NiFi has died, the Bootstrap is able to send notifications of these events
|
||||
to interested parties. This is configured by specifying an XML file that defines which notification services can be used. More about this
|
||||
file can be found in the <<notification_services>> section.
|
||||
|
|
Loading…
Reference in New Issue