GitHub user mcgilman opened a pull request:

    https://github.com/apache/nifi/pull/1247

    Introducing restricted components which require additional access

    NIFI-3050:
    - Introducing a Restricted annotation for components that require elevated 
privileges to use.
    - Updating the new Processor, Controller Service, and Reporting Task 
dialogs to include these details and prevent unauthorized selection.
    - Including the Restricted description in the generated component 
documentation.
    - Updating processor access control integration test to verify restricted 
component creation.
    - Updating the developer, user, and admin guide to include the restricted 
component policy.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mcgilman/nifi NIFI-3050

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/1247.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 #1247
    
----
commit 890c42bb79d9b57ce7ed3e4d547337d76e741bc1
Author: Matt Gilman <[email protected]>
Date:   2016-11-18T21:19:04Z

    NIFI-3050:
    - Introducing a Restricted annotation for components that require elevated 
privileges to use.
    - Updating the new Processor, Controller Service, and Reporting Task 
dialogs to include these details and prevent unauthorized selection.
    - Including the Restricted description in the generated component 
documentation.
    - Updating processor access control integration test to verify restricted 
component creation.
    - Updating the developer, user, and admin guide to include the restricted 
component policy.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to