[jira] [Commented] (NIFI-15791) Add per-secret TTL cache to ParameterProviderSecretsManager

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-15791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18071521#comment-18071521 ] 

ASF subversion and git services commented on NIFI-15791:
--------------------------------------------------------

Commit a671bc2653863893bda0ae84bcd3fd4ca8c37511 in nifi's branch refs/heads/main from Pierre Villard
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a671bc26538 ]

NIFI-15791 Added Secret Caching to ParameterProviderSecretsManager (#11100)

Signed-off-by: David Handermann <ex...@apache.org>

> Add per-secret TTL cache to ParameterProviderSecretsManager
> -----------------------------------------------------------
>
>                 Key: NIFI-15791
>                 URL: https://issues.apache.org/jira/browse/NIFI-15791
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Pierre Villard
>            Assignee: Pierre Villard
>            Priority: Major
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> Adds a TTL-based cache for resolved secret values in ParameterProviderSecretsManager to avoid redundant calls to ParameterProvider.fetchParameterValues() on every secret lookup. Each secret is cached independently by its fully qualified name and expires after a configurable TTL (default 5 minutes). Caching can be disabled by setting the TTL to 0 sec.
> A follow-up improvement will be done to expose an API to invalidate the cache in case a user wants to force the refresh on the secrets while configuring a connector.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)