Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cache Invalidation Upon Store Update? #627

Open
daniel-klingensmith-jamf opened this issue Sep 19, 2024 · 0 comments
Open

Cache Invalidation Upon Store Update? #627

daniel-klingensmith-jamf opened this issue Sep 19, 2024 · 0 comments

Comments

@daniel-klingensmith-jamf

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 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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant