[ 
https://issues.apache.org/jira/browse/NIFI-16404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Gilman updated NIFI-16404:
-------------------------------
    Fix Version/s: 2.13.0
       Resolution: Fixed
           Status: Resolved  (was: Patch Available)

> Provide connector-scoped access to managed Process Group configuration
> ----------------------------------------------------------------------
>
>                 Key: NIFI-16404
>                 URL: https://issues.apache.org/jira/browse/NIFI-16404
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: Rob Fellows
>            Assignee: Rob Fellows
>            Priority: Major
>             Fix For: 2.13.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Process Groups managed by a Connector cannot be retrieved through the 
> standard Process Group REST resource unless the Connector is in 
> Troubleshooting mode.
> This restriction is intentional for general component operations: 
> connector-managed flow components should not be directly accessible while the 
> Connector owns and manages its flow. However, it also prevents clients with 
> read access to the Connector from retrieving the configuration of a managed 
> Process Group for read-only inspection.
> The Connector REST resource currently exposes:
> * Connector flow retrieval, returning a ProcessGroupFlowEntity containing 
> canvas contents and breadcrumb information
> * Connector-scoped retrieval of individual Controller Services
> * Connector-scoped status and status-history operations for managed Process 
> Groups
> It does not expose an equivalent operation that returns a complete 
> ProcessGroupEntity. A ProcessGroupFlowEntity does not contain all Process 
> Group configuration fields, permissions, and revision information needed by 
> clients that display Process Group configuration.
> Consequently, clients must either:
> 1. Use the standard Process Group endpoint, which fails while the Connector 
> is not in Troubleshooting mode
> 2. Work with an incomplete representation from the Connector flow endpoint
> 3. Require Troubleshooting mode merely to inspect configuration, even though 
> no modification is being requested
> A client with read access to a Connector should be able to retrieve the 
> complete configuration entity for a Process Group belonging to that 
> Connector’s managed flow, regardless of whether the Connector is in 
> Troubleshooting mode. This capability must not make unrelated Process Groups 
> accessible through the Connector or weaken the existing restrictions on 
> standard Process Group operations.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to