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

ASF subversion and git services commented on NIFI-14550:
--------------------------------------------------------

Commit dd8b87f6f9f374f367666d4311199bbdf29cd2e2 in nifi's branch 
refs/heads/main from Bryan Bende
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=dd8b87f6f9 ]

NIFI-14550 Allow setting version control info on a non-versioned process group
- Update stopVersionControl to no longer clear versioned component ids in order 
to allow re-attaching later
- Add new methods to service facade and PG DAO to pass the flow snapshot when 
setting VCI
- Fix system test to ensure UP_TO_DATE after Set Version Info

Signed-off-by: Pierre Villard <[email protected]>

This closes #9930.


> Allow an unversioned PG to start tracking to a version in a registry client
> ---------------------------------------------------------------------------
>
>                 Key: NIFI-14550
>                 URL: https://issues.apache.org/jira/browse/NIFI-14550
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Bryan Bende
>            Assignee: Bryan Bende
>            Priority: Major
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> This improvement is to add a new REST API that will allow updating an 
> unversioned PG to be under version control and tracking to an existing flow 
> in a selected registry client. Which is different from Start Version Control 
> which creates a whole new flow in the registry client. A similar analogy 
> might be having a local git repo and adding a remote to track to.



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

Reply via email to