[
https://issues.apache.org/jira/browse/NIFI-14645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18058050#comment-18058050
]
Rahul Verma commented on NIFI-14645:
------------------------------------
pg-change-all-versions output:
Name Id Prev
Version New Version Message
-------------------------- ------------------------------------
------------ -----------
--------------------------------------------------------------------
fp-secureSourceWithXMLdata 5078bc4e-019c-1000-0000-00004721a0f3 11
12 Process group cannot be upgraded because current state is
UP_TO_DATE
I think internal state sync takes time, so because of that change-all-versions
is not working as expected, i was trying to automate my upgrades and hit this
issue.
It clearly shows 11 and 12 version and says UP_TO_DATE
> Toolkit CLI - improve change version for versioned PG and PG listing
> --------------------------------------------------------------------
>
> Key: NIFI-14645
> URL: https://issues.apache.org/jira/browse/NIFI-14645
> Project: Apache NiFi
> Issue Type: Improvement
> Components: SDLC, Tools and Build
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
> Fix For: 2.5.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> (I'm happy to break down the below into multiple issues/PRs if preferred but
> given the very limited amount of code changes, I put everything together)
> * Add recursive flag support to PG List command
> * Fix PG Change Version to account for the branch feature
> * Made optional the Flow ID in PG Change All Versions so that it is possible
> to upgrade all versioned flows to the latest available version
> * Fix Upload Bundles command when recursive flag is set
> * Add version control state to Process Groups Result to show if a process
> group is versioned and if yes, what's the associated state
> * Add branch name to Version Control Info Result to show the branch name, if
> any
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
