[
https://issues.apache.org/jira/browse/NIFIREG-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17329136#comment-17329136
]
John Wise commented on NIFIREG-179:
-----------------------------------
Ideally, the current flow UUID would be maintained, so that process groups
deployed in a NiFi flow don't need to be replaced. From the command-line,
nfcli's "registry sync-flow-versions" requires that a new destination UUID be
created in the bucket to move an existing flow to, which is what creates the
disconnect. Ideally, that command would just move the existing UUID from the
old bucket to the new bucket. Any UI implementation would work the same way.
> Move Flow to other buckets and rename them
> ------------------------------------------
>
> Key: NIFIREG-179
> URL: https://issues.apache.org/jira/browse/NIFIREG-179
> Project: NiFi Registry
> Issue Type: Improvement
> Affects Versions: 0.1.0, 0.2.0
> Reporter: Julian Gimbel
> Priority: Minor
>
> It should be possible to move a versioned flow from one bucket to another in
> the UI.
> In addition it should be possible to change the Flow Name for versioned flows.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
