Craig Patrick created NIFI-14925:
------------------------------------
Summary: Updating "Reference Parameters" in contexts will not
change, and keeps referencing original service ID causing errors
Key: NIFI-14925
URL: https://issues.apache.org/jira/browse/NIFI-14925
Project: Apache NiFi
Issue Type: Bug
Components: Core Framework
Affects Versions: 2.0.0
Environment: All
Reporter: Craig Patrick
Attachments: image-2025-09-01-15-51-40-367.png
When setting a "Reference Parameter" for a service and then trying to change
this in a different environment the process for changing the ID fails and
requires a workaround.
Use Case:
I have a *HandleHTTPRequest* which we need to have SSL context for in some
environments and not others (locally for example). This was all set up in the
DEV environment using a *Reference Parameter* to decide whether or not an SSL
Context Service should be used - which works fine.
However, when deploying this to another environment (local or QA for example)
and then editing the subsequent parameter to change or remove the ID (when we
don't want SSL) - we continually see the following error message:
!image-2025-09-01-15-51-40-367.png!
Every time I try and edit the parameter it will not let me apply because it
continuously tries to reference the service ID from a different environment
(which doesn't exist of course).
The only way around this is:
# Remove the Reference Parameter from the HandleHTTPRequest Processor
# Update the parameter in the context to reference the correct service ID (or
set to empty)
# Go back into the processor and set the Reference Parameter back to the
required param once more.
Only then will it allow it to be updated and not show the error looking for the
original service ID and not register that there was a local change which needs
to be committed.
It's as if it's not updating before refreshing the services associated with the
parameter context
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
