refactor: use stellate plugin instead of custom code for graphql cache management

[ccorda]

Curently we have a webhooks.php file that pings a Next.js route to purge the stellate cache. It's a crude implementation that only implements purgeAll.

This PR will look to remove our custom code and use the Stellate WP plugin to purge directly.

Testing (as we go from purgeAll to granular, need to make sure we're not introducing errors):

• [ ] Does updating a page successfully purge that page? (check for content and status changes)
• [ ] Does updating a post successfully purge that page? (check for content and status changes)
• [ ] Does update a custom post type successfully purge both the custom post type and index?
• [ ] Does adding/removing redirection redirects successfully purge globals
• [ ] Does adding/removing menus successfully purge globals
• [ ] Does editing ACF theme options successfully purge globals

We'll also want to look at how we clone environments (from prod to staging and local), to make sure we're not clearing the cache as we do staging or local development.

closes #226 closes #204

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
bubs-next	✅ Ready (Inspect)	Visit Preview		May 10, 2024 6:53am

[ccorda]

Should https://github.com/patronage/bubs-next/blob/main/website/src/pages/api/graphcdn.js go away now?

[ccorda]

@chrisherold implemented this this morning on a site and left a few more comments on code.

One issue I'm running into is that it works when I update /sample-page, but not when I update the homepage:

[chrisherold]

Should https://github.com/patronage/bubs-next/blob/main/website/src/pages/api/graphcdn.js go away now?

yep, removed

[chrisherold]

@chrisherold implemented this this morning on a site and left a few more comments on code.

One issue I'm running into is that it works when I update /sample-page, but not when I update the homepage:

updated