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

Provide default implementation for purging Acquia Platform CDN from invalidation/revalidation events. #124

Open
fiasco opened this issue Sep 26, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@fiasco
Copy link
Contributor

fiasco commented Sep 26, 2022

Describe the solution you'd like
When static content is regenerated, we should be able to notify Acquia Platform CDN and purge corresponding URLs after they've been regenerated.

@fiasco fiasco added the enhancement New feature or request label Sep 26, 2022
@joshirohit100
Copy link
Contributor

Noticed that next drupal module also has next_extra (experimetal though) that allows to re-validate in nextjs app - https://next-drupal.org/guides/on-demand-revalidation

I think in same process we can utilise to purge the cache from CDN as well while re-validating from nextjs

@lauriii
Copy link
Contributor

lauriii commented Oct 13, 2022

The purging in next-drupal is unfortunately based on paths. We could potentially integrate that with Acquia Purge but I'm not sure we should. At the moment, Acquia Purge only queues purges for tags based invalidations which is the only solution that can work consistently out-of-the-box. The path based invalidation will always require developer intervention since it is very hard for us to predict which paths should be invalidated.

Ideally we could resolve this after #17 is done.

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

No branches or pull requests

3 participants