Miguel Angel Garcia Reguera created NIFI-16516:
--------------------------------------------------
Summary: Parameter Contexts & Flow Versioning
Key: NIFI-16516
URL: https://issues.apache.org/jira/browse/NIFI-16516
Project: Apache NiFi
Issue Type: Improvement
Components: Flow Versioning
Reporter: Miguel Angel Garcia Reguera
*Observed Behavior*
When promoting a versioned Process Group across environments using Apache NiFi
Registry, the resulting behavior appears to be that the complete definition of
associated Parameter Contexts is included in the versioned flow snapshot rather
than only maintaining a logical association between the Process Group and the
Parameter Context.
According to the Apache NiFi documentation, Parameter Contexts are intended to
enable supplying different parameter values to the same flow in different NiFi
instances and environments. They are presented as a mechanism for making flows
portable across environments. However, a Versioned Flow Snapshot contains a
{{parameterContexts}} section as part of the serialized flow definition.
In practice, this means that when a flow version is imported or upgraded in
another environment, NiFi attempts to reconcile or update the Parameter Context
definition contained in the snapshot, including Parameter Provider-managed
parameters.
This behavior becomes problematic when Parameter Contexts are
environment-specific and especially when they are managed through Parameter
Providers such as HashiCorp Vault, Kubernetes Secrets, or environment
variables. Parameter Provider-generated contexts are intended to be maintained
locally in each environment and may differ in configuration, provider
identifiers, or retrieved parameter values.
*Expected Behavior*
When promoting a versioned Process Group between environments, it should be
possible to preserve the target environment's existing Parameter Context
association and configuration.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
