Gabriel Orstadius-Bui created NIFI-15697:
--------------------------------------------
Summary: Using external Service in Versioned PG leads to
inconsistent versioning state
Key: NIFI-15697
URL: https://issues.apache.org/jira/browse/NIFI-15697
Project: Apache NiFi
Issue Type: Bug
Components: Flow Versioning
Affects Versions: 2.8.0
Reporter: Gabriel Orstadius-Bui
How to reproduce:
# Create a versioned PG with a processor that uses an external service and
commit changes. (E.g. an InvokeHttp which uses a StandardSSLContextService in
the root PG).
# In the processor, edit the service-property and use a different external
service (E.g. use different StandardSSLContextService). The PG is now
(sometimes?) marked as being Locally Modified, and the "Show Local
Change"-Dialog shows that the property was changed.
# Delete the previously used service.
# The PG is still marked as Locally Modified, but the "Show Local
Change"-dialog now longer shows any local changes.
The fact that the PG is now marked as Locally Modified now prevents the user
from e.g. changing to a different Flow version. User must revert/commit local
changes (even if there aren't any) in order for the PG to no longer be marked
as Locally Modified.
There seems to be inconsistencies with when changing a Processor's reference to
an external Service counts as Local Change and/or the PG counting as Locally
Modified (sometimes step 2 does not register as a Local Change or the PG
becoming Locally Modified)
I can see arguments for and against such changes counting as a Local Change,
but the rule should be clear and it should never be the case that the PG is
marked as Locally Modified but that there isn't any Local Changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
