[
https://issues.apache.org/jira/browse/NIFI-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16637216#comment-16637216
]
Bryan Bende commented on NIFI-5657:
-----------------------------------
[~rthomasson] the transfer-flow-version command is used to transfer a version
of a flow to another existing flow, so since the existing flow already exists
in a bucket, the bucket id is implied because it has to be the bucket where the
destination flow exists.
To transfer across buckets you would do something like:
create-flow -bid <DEST_BUCKET> -fn "My Second Flow"
This command would return the flow id of the newly created flow in the bucket
specified by DEST_BUCKET, then use this flow id in the command below for
DEST_FLOW_ID:
transfer-flow-version -sf <SOURCE_FLOW_ID> -sfv <SOURCE_FLOW_VERSION> -f
<DEST_FLOW_ID>
> NiFi Toolkit - Add optional destination bucket ID parameter to NiFi CLI
> command: registry transfer-flow-version
> ---------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-5657
> URL: https://issues.apache.org/jira/browse/NIFI-5657
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools and Build
> Affects Versions: 1.7.0, 1.7.1
> Reporter: Randy Thomasson
> Priority: Minor
>
> Modify the CLI registry transfer-flow-version command to support an optional
> parameter for a destination bucket ID. This will allow users of the cli
> command to designate a specific bucket for the destination flow and would
> increase the usefulness of this command as it would allow the command to be
> used to transfer flows between buckets within the same registry instance.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
