mirror of https://github.com/apache/nifi.git
NIFI-8150 Change Download flow to Download flow definition for process groups (#4766)
This commit is contained in:
Andrew Lim
GitHub
parent
803ba882aa
commit
27f57e6463
|
|
@ -1610,7 +1610,7 @@ If it is not possible to install the unlimited strength jurisdiction policies, t
|
|||
It is preferable to request upstream/downstream systems to switch to link:https://cwiki.apache.org/confluence/display/NIFI/Encryption+Information[keyed encryption^] or use a "strong" <<key-derivation-functions, Key Derivation Function (KDF) supported by NiFi>>.
|
||||
|
||||
[[nifi_sensitive_props_key]]
|
||||
== Encrypted Passwords in Flow Definitions
|
||||
== Encrypted Passwords in Flows
|
||||
|
||||
NiFi always stores all sensitive values (passwords, tokens, and other credentials) populated into a flow in an encrypted format on disk. The encryption algorithm used is specified by `nifi.sensitive.props.algorithm` and the password from which the encryption key is derived is specified by `nifi.sensitive.props.key` in _nifi.properties_ (see <<security_configuration,Security Configuration>> for additional information). Prior to version 1.12.0, the list of available algorithms was all password-based encryption (PBE) algorithms supported by the `EncryptionMethod` enum in that version. Unfortunately many of these algorithms are provided for legacy compatibility, and use weak key derivation functions and block cipher algorithms & modes of operation. In 1.12.0, a pair of custom algorithms was introduced for security-conscious users looking for more robust protection of the flow sensitive values. These options combine the <<argon2-kdf, Argon2id>> KDF with reasonable cost parameters (2^16^ or `65,536 KB` of memory, `5` iterations, and parallelism `8`) with an authenticated encryption with associated data (AEAD) mode of operation, `AES-G/CM` (Galois Counter Mode). The algorithms are specified as:
|
||||
|
||||
|
|
@ -1654,7 +1654,7 @@ In the future, we hope to provide supplemental documentation that covers the NiF
|
|||
image::zero-leader-cluster-http-access.png["NiFi Cluster HTTP Access"]
|
||||
|
||||
=== Zero-Leader Clustering
|
||||
NiFi employs a Zero-Leader Clustering paradigm. Each node in the cluster has an identical flow definition and performs the same tasks on
|
||||
NiFi employs a Zero-Leader Clustering paradigm. Each node in the cluster has an identical flow and performs the same tasks on
|
||||
the data, but each operates on a different set of data. The cluster automatically distributes the data throughout all the active nodes.
|
||||
|
||||
One of the nodes is automatically elected (via Apache
|
||||
|
|
|
|||
|
|
@ -370,7 +370,7 @@ NOTE: It is also possible to double-click on the Process Group to enter it.
|
|||
- *View connections->Downstream*: This option allows the user to see and "jump to" downstream connections that are going out of the Process Group.
|
||||
- *Center in view*: This option centers the view of the canvas on the given Process Group.
|
||||
- *Group*: This option allows the user to create a new Process Group that contains the selected Process Group and any other components selected on the canvas.
|
||||
- *Download flow*: This option allows the user to download the flow as a JSON file. The file can be used as a backup or imported into a link:https://nifi.apache.org/registry.html[NiFi Registry^] using the <<toolkit-guide.adoc#nifi_CLI,NiFi CLI>>. (Note: If "Download flow" is selected for a versioned process group, there is no versioning information in the download. In other words, the resulting contents of the JSON file is the same whether the process group is versioned or not.)
|
||||
- *Download flow definition*: This option allows the user to download the flow definition of the process group as a JSON file. The file can be used as a backup or imported into a link:https://nifi.apache.org/registry.html[NiFi Registry^] using the <<toolkit-guide.adoc#nifi_CLI,NiFi CLI>>. (Note: If "Download flow definition" is selected for a versioned process group, there is no versioning information in the download. In other words, the resulting contents of the JSON file is the same whether the process group is versioned or not.)
|
||||
- *Create template*: This option allows the user to create a template from the selected Process Group.
|
||||
- *Copy*: This option places a copy of the selected Process Group on the clipboard, so that it may be pasted elsewhere on the canvas by right-clicking on the canvas and selecting Paste. The Copy/Paste actions also may be done using the keystrokes Ctrl-C (Command-C) and Ctrl-V (Command-V).
|
||||
- *Empty all queues*: This option allows the user to empty all queues in the selected Process Group. All FlowFiles from all connections waiting at the time of the request will be removed.
|
||||
|
|
|
|||
|
|
@ -1588,7 +1588,7 @@
|
|||
window.open(uri);
|
||||
}).fail(function () {
|
||||
nfDialog.showOkDialog({
|
||||
headerText: 'Download Flow',
|
||||
headerText: 'Download Flow Definition',
|
||||
dialogContent: 'Unable to generate access token for downloading content.'
|
||||
});
|
||||
});
|
||||
|
|
|
|||
|
|
@ -841,7 +841,7 @@
|
|||
{id: 'move-into-parent-menu-item', condition: canMoveToParent, menuItem: {clazz: 'fa fa-arrows', text: 'Move to parent group', action: 'moveIntoParent'}},
|
||||
{id: 'group-menu-item', condition: canGroup, menuItem: {clazz: 'icon icon-group', text: 'Group', action: 'group'}},
|
||||
{separator: true},
|
||||
{id: 'download-menu-item', condition: supportsDownloadFlow, menuItem: {clazz: 'fa', text: 'Download flow', action: 'downloadFlow'}},
|
||||
{id: 'download-menu-item', condition: supportsDownloadFlow, menuItem: {clazz: 'fa', text: 'Download flow definition', action: 'downloadFlow'}},
|
||||
{separator: true},
|
||||
{id: 'upload-template-menu-item', condition: canUploadTemplate, menuItem: {clazz: 'icon icon-template-import', text: 'Upload template', action: 'uploadTemplate'}},
|
||||
{id: 'template-menu-item', condition: canCreateTemplate, menuItem: {clazz: 'icon icon-template-save', text: 'Create template', action: 'template'}},
|
||||
|
|
|
|||
Loading…
Reference in New Issue