Problem/Motivation

We use CloudFront, which is path-based. This allows file purging based on relative path instead of by URL.

Proposed resolution

Add a "Type" selector to the config screen allowing the user to choose between current "url" invalidation and "path" invalidation.

Remaining tasks

Review and test by maintainer.

User interface changes

Adds a "Type" dropdown to the config screen.

Issue fork purge_file-3399909

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

kevinb623 created an issue. See original summary.

kevinb623’s picture

Thanks for considering this merge. It will allow us to invalidate file paths using our path-based workflow with CloudFront.

dpi made their first commit to this issue’s fork.

dpi’s picture

Status: Active » Needs review

Added a variety of fixes and improvements.

Removed wildcard setting and consolidated to invalidation type config.

Type safety.

Added schema for existing config, config migration for new

omarlopesino’s picture

I wonder if this module should use plugins to support the different purger types, so this escalates better.

geoffreyr’s picture

This one doesn't merge with 1.1.2 or the current DEV; might try and re-roll.

omarlopesino’s picture

Working to fix merge conflicts

omarlopesino’s picture

I have changed it according to the latest changes (supporting of queue invalidation) that were conflicting with this issue.

I see the changes okay but I cannot test it as I don't have configured a site with path based cache. May somebody test it? Thanks!

mohit_aghera made their first commit to this issue’s fork.

robbertnl’s picture

This patch works for me, thank you!

omarlopesino’s picture

Status: Needs review » Fixed

Many thanks everyone! The MR is merged and the functionality is ready at 1.3.0

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.