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

Addons: activating a version doesn't purge the cache #11291

Open
humitos opened this issue Apr 18, 2024 · 0 comments
Open

Addons: activating a version doesn't purge the cache #11291

humitos opened this issue Apr 18, 2024 · 0 comments
Labels
Accepted Accepted issue on our roadmap Improvement Minor improvement to code

Comments

@humitos
Copy link
Member

humitos commented Apr 18, 2024

When the use activates a new version, the addons API response doesn't immediately reflect this change. This is because the API response is cached. However, triggering a purge on that project won't immediately work since the version won't be built=True at that point yet.

So, we need to figure it out how to purge the cache on "new active versions, but only once they have finished successfully". How we can detect this?

@humitos humitos added Improvement Minor improvement to code Accepted Accepted issue on our roadmap labels Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accepted Accepted issue on our roadmap Improvement Minor improvement to code
Projects
Status: Planned
Development

No branches or pull requests

1 participant