Bryan Rosander created NIFI-3604:
------------------------------------
Summary: MiNiFi Initial Command and Control Server Implementation
Key: NIFI-3604
URL: https://issues.apache.org/jira/browse/NIFI-3604
Project: Apache NiFi
Issue Type: Improvement
Reporter: Bryan Rosander
A lot of work (MINIFI-2, MINIFI-4, MINIFI-12, MINIFI-14, MINIFI-17, MINIFI-36)
has gone into creating a configurable way for MiNiFi to get new configuration
from a defined source.
This is one aspect of the overal [the command and control feature
proposoal|https://cwiki.apache.org/confluence/display/MINIFI/MiNiFi+Command+and+Control].
The other aspect is an endpoint that ties into the NiFi ideas of [flow
versioning|https://cwiki.apache.org/confluence/display/NIFI/Configuration+Management+of+Flows#ConfigurationManagementofFlows-FlowVersioning]
and probably the [variable
registry|https://cwiki.apache.org/confluence/display/NIFI/Variable+Registry].
While the flow registry is not available for consumption yet, we can still
start proving out things from the MiNiFi end forward. We can start by
implementing a server MiNiFi can get configuration from that is done in a
pluggable way such that it can be integrated with the NiFi registries mentioned
above when they are ready for consumption.
This server should:
1. Utilize same/similar paradigms of the NiFi webserver to facilitate reuse and
possible future embedding.
2. Support pluggability for its main functions including security and logic for
retrieving the MiNiFi configuration.
3. Support both authentication of users and authorization for a given flow.
4. Integrate easily with the existing PullHttpChangeIngestor in MiNiFi.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
