[ 
https://issues.apache.org/jira/browse/NIFIREG-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428499#comment-16428499
 ] 

ASF GitHub Bot commented on NIFIREG-158:
----------------------------------------

Github user bbende commented on the issue:

    https://github.com/apache/nifi-registry/pull/108
  
    @kevdoran ok good to go now, ended up adding all of the GET operations from 
BucketFlowResource that could be done without a bucket id...
    
    ```
    /flows/{flowId}
    /flows/{flowId}/versions/{version}
    /flows/{flowId}/versions/latest
    /flows/{flowId}/versions/latest/metadata
    /flows/{flowId}/versions
    ```


> Should be able to retrieve a flow by id without the bucket it
> -------------------------------------------------------------
>
>                 Key: NIFIREG-158
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-158
>             Project: NiFi Registry
>          Issue Type: Improvement
>    Affects Versions: 0.1.0
>            Reporter: Bryan Bende
>            Assignee: Bryan Bende
>            Priority: Minor
>
> Currently all the flow end-points are nested under a bucket, like:
> {code:java}
> /buckets/{bucketId}/flows/{flowId}
> /buckets/{bucketId}/flows/{flowId}/versions/{version}{code}
> The flow identifier is unique across all buckets, so once the flow is create 
> we should be able to support end-points without the bucket id:
> {code:java}
> /flows/{flowId}
> /flows/{flowId}/versions/{version}
> {code}
> We still need to look at the bucket and authorize the bucket id when secure, 
> but we'll have the bucket id from retrieving the flow.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to