[
https://issues.apache.org/jira/browse/NIFI-14269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18010045#comment-18010045
]
Pierre Villard commented on NIFI-14269:
---------------------------------------
That should not be the case. We did change things so that parameter values
coming via a provider are no longer persisted on disk (only kept in memory for
better security). In case of a reboot, when NiFi is starting all of the
components, the fetch will be executed automatically on the provider(s) to have
the values of the parameters. But if a parameter has been deleted on the
provider side (say AWS Secret Manager), you'd have to manually call the fetch
to have it removed from the parameter context, otherwise it'd remain there with
an empty value. If you observe something else, let me know.
> Parameter Context - Cannot delete parameter from unreferenced/new provider
> context
> ----------------------------------------------------------------------------------
>
> Key: NIFI-14269
> URL: https://issues.apache.org/jira/browse/NIFI-14269
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 2.3.0, 2.4.0, 2.5.0
> Reporter: Bill Kinzel
> Assignee: Pierre Villard
> Priority: Major
> Labels: ParameterContext
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 1.) Via UI - Fetch a new provider context (at least two rows) from Aws or
> Database Provider (Leave Unreferenced)
> 2.) Remove a single parameter from the source
> 3.) Re-fetch from the same parameter provider
> 4.) Apply (no Errors)
> Parameter never goes away
> The asterisk next to the parameter states it's still being referenced, but is
> not...it is a new/unreferenced parameter in a new unreferenced parameter
> context.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
