[
https://issues.apache.org/jira/browse/MINIFI-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930773#comment-15930773
]
ASF GitHub Bot commented on MINIFI-238:
---------------------------------------
GitHub user brosander opened a pull request:
https://github.com/apache/nifi-minifi/pull/75
MINIFI-238 - MiNiFi Initial Command and Control Server Implementation
Thank you for submitting a contribution to Apache NiFi - MiNiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [X] Does your PR title start with MINIFI-XXXX where XXXX is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [X] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [X] Is your initial contribution a single, squashed commit?
### For code changes:
- [X] Have you ensured that the full suite of tests is executed via mvn
-Pcontrib-check clean install at the root nifi-minifi folder?
- [X] Have you written or updated unit tests to verify your changes?
- [X] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [X] If applicable, have you updated the LICENSE file, including the main
LICENSE file under minifi-assembly?
- [X] If applicable, have you updated the NOTICE file, including the main
NOTICE file found under minifi-assembly?
### For documentation related changes:
- [X] Have you ensured that format looks appropriate for the output in
which it is rendered?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/brosander/nifi-minifi MINIFI-238
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi-minifi/pull/75.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #75
----
commit f1d2c21070321bf9abbb97f9885344a20b546d8b
Author: Bryan Rosander <[email protected]>
Date: 2017-03-01T22:06:11Z
MINIFI-238 - MiNiFi Initial Command and Control Server Implementation
----
> MiNiFi Initial Command and Control Server Implementation
> --------------------------------------------------------
>
> Key: MINIFI-238
> URL: https://issues.apache.org/jira/browse/MINIFI-238
> Project: Apache NiFi MiNiFi
> Issue Type: New Feature
> 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)
