How do I deal with KVM cache when updating the Key Value Map with a PUT operation?

[nagashree_b]

Is there a way to mimic the PUT operation in the KVM Operations policy through a management API?

Here is my usecase -

I have a set of KVMs that get updated not so often, but periodically.

1. Backend Authorization Key rotation (happens once in 45 days)

2. Maintenance Mode settings for the backend (irregular, but can assume once in 3 months)

3. Backend account credentials update for legacy systems (once in 60 days)

The operations team does the update on the Management UI, however the cache will not reflect the values until the current expiry (which is set to 1 hour, 1 day etc)

I checked a few other posts - mapidentifier cannot be set to a dynamic value, so I cant have a single utility proxy that can update the entries and values based on an input KVM name.

I have tried a not so clean way of having a single proxy which has multiple KVM policies (one for each mapidentifier) and conditions to execute the corresponding policy based on a request payload element which has the KVM name. The issue is, if the number of KVMs(right now 3) that need periodic updates keep increasing, I have to keep adding more KVM operations policy to this proxy.

Can anyone suggest any options on how to handle this scenario?