[
https://issues.apache.org/jira/browse/NIFI-16058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard updated NIFI-16058:
----------------------------------
Component/s: Flow Versioning
(was: Core Framework)
> 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: Flow Versioning
> 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
> Assignee: Pierre Villard
> 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 ListenHTTP
> 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.
> In earlier versions of NiFi we have created a "Generic/Universal HTTP
> Service" process group which we reuse in multiple places, and change the SSL
> Context in order to use the correct certificate for different web services.
> Changing the SSL Context to another external SSLContextService with a
> different name has never been consider a change.
> Now in version 2.10.0 changing the SSL Context to another external
> SSLContextService are seeing as a local change
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
