[NIFI-8907] Variable Registry properties that are expected for a versioned Flow should be tracked

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: NiFi Registry
• Assignee: Unassigned
• Reporter: Joe Percivall
• Created: 22/Dec/17 02:45
• Updated: 30/Jan/23 16:13

Description

As a user, pulling down a new versioned flow, I'd like to know which properties are expected in my NiFi's Variable Registry to run the flow. By explicitly calling these out I can more easily configure and understand the flow on deployment. Also, would facilitate maintainability.

An easy example of a typical flow that would utilize this is one that relies on an external source which is configured per environment (SSL file paths, Web service URL, etc.).

This could also pave the way to set "default" variables within a Registry instance and elsewhere.

Issue Links

• links to: GitHub Pull Request #2219