[
https://issues.apache.org/jira/browse/NIFI-16058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18092835#comment-18092835
]
Jens M Kofoed commented on NIFI-16058:
--------------------------------------
Dear [~pvillard] and [~exceptionfactory] I can see that you both have been
working on different registry client related features in the release for 2.10.0
I hope this bug could be fixed so we can upgade to a 2.10.1 or something like
that, please
> Changing the SSL Context in processor generate a local change in version
> control
> --------------------------------------------------------------------------------
>
> Key: NIFI-16058
> URL: https://issues.apache.org/jira/browse/NIFI-16058
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 2.10.0
> Environment: Ubuntu 24.4
> openjdk version "21.0.11" 2026-04-21
> NiFi v. 2.10.0
> Reporter: Jens M Kofoed
> Priority: Major
>
> We just upgraded our dev cluster from v. 2.9.0 to 2.10.0 and see a version
> control issue.
> We have a process group which is under version control and have an InvokeHTTP
> process in this group. Changing the SSL Context is now consider a local
> change in the version control.
> This was not the case in version 2.9.0 and below. We are using the
> GitLabFlowRegistryClient for version control.
> After downgrading back to v. 2.9.0 changing the SSL Context for InvokeHTTP
> processor are not considering a local change in the version control
> It seems like some changes has created a bug (GitLabFlowRegistryClient???)
> The same is happening for HandleHttpResponse. If you change the SSL Context,
> it will trigger a "local change" in version control.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
