[
https://issues.apache.org/jira/browse/NIFI-15452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18051261#comment-18051261
]
ASF subversion and git services commented on NIFI-15452:
--------------------------------------------------------
Commit c2604cb790636bd6616b73d35b69acadd9d662bd in nifi's branch
refs/heads/main from Pierre Villard
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=c2604cb790 ]
NIFI-15452 Changed FlowRegistryClient instances to always require validation
(#10757)
Signed-off-by: David Handermann <[email protected]>
> FlowRegistryClient validation not triggered when properties change at runtime
> -----------------------------------------------------------------------------
>
> Key: NIFI-15452
> URL: https://issues.apache.org/jira/browse/NIFI-15452
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When adding or modifying properties on a FlowRegistryClient (e.g.,
> GitHubFlowRegistryClient) at runtime through the UI, validation is not
> re-triggered, causing the component to remain in a VALID state even when
> invalid properties are configured. The validation errors only appear after a
> NiFi restart.
> h3. Steps to Reproduce
> # Create a FlowRegistryClient (e.g., GitHubFlowRegistryClient) and configure
> it with valid properties
> # Verify the component shows as VALID
> # Edit the registry client and add a dynamic property (e.g., test=test)
> # Save the configuration
> # Observe that the component still shows as VALID despite the dynamic
> property being unsupported
> # Restart NiFi
> # After restart, the component now shows as INVALID with the error: 'test'
> is not a supported property or has no Validator associated with it
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
