[
https://issues.apache.org/jira/browse/NIFI-2933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-2933:
-----------------------------
Resolution: Fixed
Fix Version/s: 1.10.0
Status: Resolved (was: Patch Available)
> Remote input/output ports and local process groups should be treated as
> completely different components
> -------------------------------------------------------------------------------------------------------
>
> Key: NIFI-2933
> URL: https://issues.apache.org/jira/browse/NIFI-2933
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Affects Versions: 1.0.0
> Reporter: Matthew Clarke
> Assignee: Koji Kawamura
> Priority: Major
> Fix For: 1.10.0
>
> Time Spent: 9.5h
> Remaining Estimate: 0h
>
> With the addition of Multi-tenancy users can restrict users to particular
> process groups. What these users cannot do is create input and output ports
> on the root canvas. Users should be able to create remote input/output ports
> within process groups and assign S2S policies to them. The only thing they
> should need an admin to do is add Servers as users and add the global
> "retrieve site-to-site details" policy. This allows for a better separation
> between dataflow designer/implementor/DFM and NiFi Admin. The added benefit
> of treating remote and local input/output ports as unique components is that
> you could add them anywhere in your flow including imbedded within process
> groups.
> Perhaps making them configurable as local or remote ports (defaulting to
> remote when added to root canvas and local when added within process group).
> This way we preserve backwards compatibility while still improving their
> usability in a multi-tenancy environment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
