- Issue created by @luke.leber
- 🇺🇸United States bkosborne New Jersey, USA
Just a note that if/when we implement this, we'll need a release note to indicate that the entire Cloudflare cache should be purged, because all the cache tags will have changed.
- 🇺🇸United States bkosborne New Jersey, USA
This is closely related to ✨ Add optional Environment setting Needs review . In fact, the solution here should be bundled with that change IMO.
- 🇺🇸United States bkosborne New Jersey, USA
A site's UUID wouldn't be ideal here because we also need to ensure the hash tags are unique per a site's environments. E.g., if the site is synced from prod to a test environment, it will have the same UUID but shouldn't share the same cache tag "namespace" with production.
Using hostname is a safer choice, but still not perfect. I imagine people are using Drush for Purge invalidations, likely via cron. Some people may not be setting the hostname when invoking Drush, so it will end up being "default" or something, so the tags wouldn't be invalidated correctly.
Not sure what other option there is though. Perhaps make the cache tag prefix configurable and let the site owner decide?
- 🇺🇸United States luke.leber Pennsylvania
UUID+hostname seems agreeable to me. Should be easy enough to improve upon iteratively if needed.
There's no issue with using multiple inputs for a more unique hash if it catches the 80%.
I think that cache collisions here might actually warrant a meta issue because there's just so much complexity involved. If Drupal didn't have the potential for such large headers this would be a lot easier to solve holistically.