You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been looking into some inconsistent responses and trying to get to the bottom of it. Consistently reproducing them has been a pain, so I've been looking everywhere and finding some interesting things along the way, thus some of my previous Issues.
I'm looking through ResponseFileServiceImpl and StoreServiceImpl and am not seeing any cache invalidation upon updating of the values in stores. I am needing this for when I have a templated response file return different values based on the value in a store that is changed during my test. For now I'm just setting 'IMPOSTER_RESPONSE_FILE_CACHE_ENTRIES': "0", but I wanted to raise the idea of an environment variable that would signal to invalidate all caches upon the update of any stores as an alternative to not using caching at all.
Let me know what you think, and thank you for all of the great help so far!
The text was updated successfully, but these errors were encountered:
Hey @outofcoffee,
I've been looking into some inconsistent responses and trying to get to the bottom of it. Consistently reproducing them has been a pain, so I've been looking everywhere and finding some interesting things along the way, thus some of my previous Issues.
I'm looking through
ResponseFileServiceImpl
andStoreServiceImpl
and am not seeing any cache invalidation upon updating of the values in stores. I am needing this for when I have a templated response file return different values based on the value in a store that is changed during my test. For now I'm just setting 'IMPOSTER_RESPONSE_FILE_CACHE_ENTRIES': "0", but I wanted to raise the idea of an environment variable that would signal to invalidate all caches upon the update of any stores as an alternative to not using caching at all.Let me know what you think, and thank you for all of the great help so far!
The text was updated successfully, but these errors were encountered: