[NIFI-6276] Better Support for Parameterizing Flows

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.10.0
• Component/s: Core Framework, Core UI
• Assignee: Matt Gilman
• Reporter: Matt Gilman
• Created: 08/May/19 20:15
• Updated: 17/Sep/19 16:08
• Resolved: 17/Sep/19 16:08

Description

This is a parent JIRA to track the introduction of the parameters. A feature proposal for describing the problem and a proposed solution can be found here [1].

[1] https://cwiki.apache.org/confluence/display/NIFI/Better+Support+for+Parameterizing+Flows

Issue Links

• is a parent of: NIFI-6606 User should not be able to select to configure a PG with a parameter context for which they do not have read permissions
• is a parent of: NIFI-6605 EL/Param tooltip not visible for large property table editors
• supercedes: NIFI-6521 Provide Encrypted Fields for Variables
• links to: GitHub Pull Request #3690

Sub-Tasks

• UI - Allow parameters to be referenced in component configuration: Resolved
• UI - create parameter context: Resolved
• UI - Support parameter reference when property contains allowable values: Resolved
• UI - Distinguish nfpr and nfel: Resolved
• UI - Allow paramter reference within EL: Resolved
• CLI - Add commands to interact with parameter contexts: Resolved
• Implement Parameter Context Backend: Resolved
• Make Parameters and Parameter Contexts searchable in UI: Resolved
• Ensure proper integration between NiFi & NiFi Registry with respect to Parameters: Resolved
• Provide auditing of changes to Parameters: Resolved
• UI - Need property editor that does not support parameters: Resolved
• UI - Allow property values to be converted into parameters: Resolved
• Add documentation for Parameters: Resolved
• UI: State of referencing processors in Parameter Context dialog do not update after "Apply": Resolved
• Parameters: "Apply" button should be greyed out if no changes have been: Resolved
• User should not be able to select to configure a PG with a parameter context for which they do not have read permissions: Resolved
• UI: Reporting Task Controller Services should not show that Parameters are supported: Resolved
• Parameters context menu item: Resolved
• CLONE - Implement Parameter Context Backend: Closed
• Support linking to unauthorized components from referencing components: Resolved
• Updating a large number of parameters causes the usage listing alignment to be pushed down: Resolved
• Usage alignment issue for invalid CS: Resolved
• Add a "Go To" button in property dialog that goes to a referenced parameter: Resolved
• UI - Indicate to the user in the Add and Edit Parameter dialogs that the value field does not support EL or Param references: Resolved
• UI - Indicate variable are no longer recommended and favor parameters: Resolved
• UI - Display the parameter context UUID: Resolved
• UI:Parameter Context dialog needs to support non-editable scenario: Resolved
• UI: Account for user permissions when showing the option to convert props to params: Resolved
• Create new parameter context option from process group config opens the new param context dialog in a read-only state.: Resolved
• UI:Parameters listed in "Reference parameter..." drop-down not listed alphabetically: Resolved
• nf-parameter-contexts.js?1.10.0-SNAPSHOT:1717 Uncaught TypeError: Cannot read property 'referencingComponents' of undefined: Resolved