I have a pipeline script that deploys KVMs using apigeetool onto our edge instance and it removes the whole KVM then creates it and adds the KVM values for all environments.
A very weird problem I have found is afterwards even if I undeploy and redeploy the latest or previous revisions of my API Proxy the old KVM value still keeps on being passed into the policy flow.
I thought it was the lookup cache but I removed that condition from the policy, I also thought it was the ExpiryTimeInSecs value from the KeyValueMapOperations but even after I set it down to 10 seconds the problem still persisted.
The only way I have found to reliably get the KVM to apply is to assign it a new value in the KVM itself, then update the KeyValueMapOperations to pull out the new value.
Has anyone else seen this before?
LinkedIn
Twitter
