You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Jens M Kofoed (Jira)" <ji...@apache.org> on 2021/02/22 10:34:00 UTC

[jira] [Commented] (NIFI-8247) Renaming a remote port is not considered as a change to be versioned

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

Jens M Kofoed commented on NIFI-8247:
-------------------------------------

[~pvillard], I do not agree.

We are using remotes ports in flows where we use versioning for the same flow in development, testing and productions flows.
 After creating a dev flow we will have a remote port named "Dev - Flow x", we import the flow as a new testing flow and the remote port will be named "copy of Dev - Flow x". Wherefore we will have to rename the new remote port to "Test - Flow x" and the next flow to "Prod - Flow x".

This will trigger a version changes, if your suggestion will be implemented. Which will break the benefit of using versioning flow across different environment. 

kind regards

Jens

 

> Renaming a remote port is not considered as a change to be versioned
> --------------------------------------------------------------------
>
>                 Key: NIFI-8247
>                 URL: https://issues.apache.org/jira/browse/NIFI-8247
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: SDLC
>            Reporter: Pierre Villard
>            Priority: Major
>
> When renaming a remote input or output port, the change is not considered as something to be versioned although it should be.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)