[
https://issues.apache.org/jira/browse/NIFI-16236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann resolved NIFI-16236.
-------------------------------------
Fix Version/s: 2.12.0
Resolution: Fixed
> Validate Parameter names during versioned flow synchronization and allow
> removal of legacy invalid Parameters
> -------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-16236
> URL: https://issues.apache.org/jira/browse/NIFI-16236
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Sevag Keosseian
> Priority: Minor
> Fix For: 2.12.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> NiFi validates Parameter names on REST create and update operations, but
> VersionedFlowSynchronizer does not apply the same validation when loading
> Parameter Contexts from a versioned flow. This allows an invalid name such as
> EXAMPLE_SECRET_\{{ environment }} to enter live state.
> Once loaded, normal REST/UI operations reject the invalid name before it can
> be removed, leaving the Parameter Context effectively locked.
> Expected behavior:
> - Reject invalid Parameter names during versioned flow synchronization.
> - Continue rejecting creation or modification of invalid names.
> - Allow deletion of legacy invalid Parameters so affected contexts can be
> repaired.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
