[
https://issues.apache.org/jira/browse/NIFIREG-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16427570#comment-16427570
]
ASF GitHub Bot commented on NIFIREG-158:
----------------------------------------
GitHub user bbende opened a pull request:
https://github.com/apache/nifi-registry/pull/108
NIFIREG-158 Added ability to retrieve flow directly by id without kno…
…wing the bucket
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bbende/nifi-registry NIFIREG-158
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi-registry/pull/108.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 #108
----
commit 216f325dc6d15134207e32db3a3c5af6c17d504e
Author: Bryan Bende <bbende@...>
Date: 2018-04-05T20:22:08Z
NIFIREG-158 Added ability to retrieve flow directly by id without knowing
the bucket
----
> 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)
